Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1635414 > unrolled thread
| Started by | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| First post | 2017-05-04 07:30 +0200 |
| Last post | 2017-05-05 12:50 +0200 |
| Articles | 9 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
[PATCH v6 4/8] ARM: dts: n8x0: Add vendor prefix to retu node Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
[PATCH v6 7/8] mfd: tps6105x: Add OF device ID table Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
[PATCH v6 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
[PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
[PATCH v6 8/8] ARM: ux500: Add vendor prefix to tps61052 node Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-04 07:30 +0200
Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Wolfram Sang <wsa@the-dreams.de> - 2017-05-04 10:20 +0200
Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Lee Jones <lee.jones@linaro.org> - 2017-05-04 14:00 +0200
Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas <javier@dowhile0.org> - 2017-05-05 12:50 +0200
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it |
| Message-ID | <tDhuV-7tw-3@gated-at.bofh.it> |
Hello, This series add OF device ID tables to mfd I2C drivers whose devices are either used in Device Tree source files or are listed in binding docs as a compatible string. That's done because the plan is to change the I2C core to report proper OF modaliases instead of always reporting a MODALIAS=i2c:<foo> regardless if a device was registered via DT or using the legacy platform data mechanism. So these patches will make sure that mfd I2C drivers modules will continue to be autoloaded once the I2C core is changed to report proper OF modalias. Users didn't have a vendor prefix in the used compatible strings, but since there wasn't a DT binding document for these drivers, it can be said that were working for mere luck and so this series fixes the users and add a DT binding doc for the drivers. Most patches can be applied independently, with the exception of patches 2 to 4 that should be applied in the same tree to keep bisect-ability. I suggest these to go through the MFD subsystem tree. Best regards, Javier Changes in v6: - Mention CBUS address instead of I2C since that's the bus used (Wolfram Sang). - Add a "i2c-cbus-gpio" comptible and use cbus0 for parent node (Wolfram Sang). - Add Wolfram Sang's Reviewed-by tag. - Add Wolfram Sang's Reviewed-by tag. - Add Wolfram Sang's Reviewed-by tag. - Add Wolfram Sang's Reviewed-by tag. Changes in v5: - Add missing properties for interrupts to DT binding doc (Rob Herring). - Add Rob Herring's Acked-by tag. - Add Aaro Koskinen's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Lee Jones <lee.jones@linaro.org>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Aaro Koskinen's Acked-by tag. - Add Tony Lindgren's Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Aaro Koskinen's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Lee Jones <lee.jones@linaro.org>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Aaro Koskinen's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Aaro Koskinen's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. - Add Lee Jones <lee.jones@linaro.org>'s Acked-by tag. - Add Rob Herring's Acked-by tag. - Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag. Changes in v4: - Use "dt-bindings: mfd:" prefix in subject line (Rob Herring). - Add information about what functions the device serve (Lee Jones). - Avoid using MFD in Device Tree (Lee Jones). - Drop -mfd suffix in compatible string (Lee Jones). - Avoid using MFD in Device Tree (Lee Jones). - Use "dt-bindings: mfd:" prefix in subject line (Rob Herring). - Add information about what functions the device serve (Lee Jones). Changes in v3: - Add a vendor prefix to the compatible string (Rob Herring). - Add a vendor prefix to the compatible string (Rob Herring). Changes in v2: - Don't use of_match_ptr() to avoid build warning when CONFIG_OF is disabled. - Don't use of_match_ptr() to avoid build warning when CONFIG_OF is disabled. Javier Martinez Canillas (8): dt-bindings: mfd: Add retu/tahvo ASIC chips bindings mfd: retu: Drop -mfd suffix from I2C device ID name mfd: retu: Add OF device ID table ARM: dts: n8x0: Add vendor prefix to retu node i2c: i2c-cbus-gpio: Add vendor prefix to retu node in example dt-bindings: mfd: Add TI tps6105x chip bindings mfd: tps6105x: Add OF device ID table ARM: ux500: Add vendor prefix to tps61052 node .../devicetree/bindings/i2c/i2c-cbus-gpio.txt | 4 ++-- Documentation/devicetree/bindings/mfd/retu.txt | 25 ++++++++++++++++++++++ Documentation/devicetree/bindings/mfd/tps6105x.txt | 17 +++++++++++++++ arch/arm/boot/dts/omap2420-n8x0-common.dtsi | 4 ++-- arch/arm/boot/dts/ste-hrefprev60.dtsi | 2 +- arch/arm/mach-omap1/board-nokia770.c | 4 ++-- drivers/mfd/retu-mfd.c | 12 +++++++++-- drivers/mfd/tps6105x.c | 8 +++++++ 8 files changed, 67 insertions(+), 9 deletions(-) create mode 100644 Documentation/devicetree/bindings/mfd/retu.txt create mode 100644 Documentation/devicetree/bindings/mfd/tps6105x.txt -- 2.9.3
[toc] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 4/8] ARM: dts: n8x0: Add vendor prefix to retu node |
| Message-ID | <tDhuV-7tw-7@gated-at.bofh.it> |
| In reply to | #1635414 |
The retu device node doesn't have a vendor prefix
in its compatible string, fix it by adding one.
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Acked-by: Tony Lindgren <tony@atomide.com>
Reviewed-by: Wolfram Sang <wsa@the-dreams.de>
---
Changes in v6:
- Add Wolfram Sang's Reviewed-by tag.
Changes in v5:
- Add Rob Herring's Acked-by tag.
- Add Aaro Koskinen's Acked-by tag.
- Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag.
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/omap2420-n8x0-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap2420-n8x0-common.dtsi b/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
index 1b06430c8013..91886231e5a8 100644
--- a/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
+++ b/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
@@ -16,7 +16,7 @@
#address-cells = <1>;
#size-cells = <0>;
retu: retu@1 {
- compatible = "retu";
+ compatible = "nokia,retu";
interrupt-parent = <&gpio4>;
interrupts = <12 IRQ_TYPE_EDGE_RISING>;
reg = <0x1>;
--
2.9.3
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 7/8] mfd: tps6105x: Add OF device ID table |
| Message-ID | <tDhuV-7tw-15@gated-at.bofh.it> |
| In reply to | #1635414 |
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:<device>.
But this could change in the future so the correct approach is to have a
OF device ID table if the devices are registered via OF.
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Lee Jones <lee.jones@linaro.org>
---
Changes in v6: None
Changes in v5:
- Add Rob Herring's Acked-by tag.
- Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag.
- Add Lee Jones <lee.jones@linaro.org>'s Acked-by tag.
Changes in v4: None
Changes in v3:
- Add a vendor prefix to the compatible string (Rob Herring).
Changes in v2:
- Don't use of_match_ptr() to avoid build warning when CONFIG_OF is disabled.
drivers/mfd/tps6105x.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/mfd/tps6105x.c b/drivers/mfd/tps6105x.c
index baa12ea666fb..187848c93779 100644
--- a/drivers/mfd/tps6105x.c
+++ b/drivers/mfd/tps6105x.c
@@ -173,9 +173,17 @@ static const struct i2c_device_id tps6105x_id[] = {
};
MODULE_DEVICE_TABLE(i2c, tps6105x_id);
+static const struct of_device_id tps6105x_of_match[] = {
+ { .compatible = "ti,tps61050" },
+ { .compatible = "ti,tps61052" },
+ { },
+};
+MODULE_DEVICE_TABLE(of, tps6105x_of_match);
+
static struct i2c_driver tps6105x_driver = {
.driver = {
.name = "tps6105x",
+ .of_match_table = tps6105x_of_match,
},
.probe = tps6105x_probe,
.remove = tps6105x_remove,
--
2.9.3
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings |
| Message-ID | <tDhuV-7tw-11@gated-at.bofh.it> |
| In reply to | #1635414 |
There are Device Tree source files defining a device node for the
retu/tahvo I2C chip, but there isn't a DT binding document for it.
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Lee Jones <lee.jones@linaro.org>
---
Changes in v6:
- Mention CBUS address instead of I2C since that's the bus used (Wolfram Sang).
- Add a "i2c-cbus-gpio" comptible and use cbus0 for parent node (Wolfram Sang).
Changes in v5:
- Add missing properties for interrupts to DT binding doc (Rob Herring).
- Add Rob Herring's Acked-by tag.
- Add Aaro Koskinen's Acked-by tag.
- Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag.
- Add Lee Jones <lee.jones@linaro.org>'s Acked-by tag.
Changes in v4:
- Use "dt-bindings: mfd:" prefix in subject line (Rob Herring).
- Add information about what functions the device serve (Lee Jones).
- Avoid using MFD in Device Tree (Lee Jones).
Changes in v3: None
Changes in v2: None
Documentation/devicetree/bindings/mfd/retu.txt | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/retu.txt
diff --git a/Documentation/devicetree/bindings/mfd/retu.txt b/Documentation/devicetree/bindings/mfd/retu.txt
new file mode 100644
index 000000000000..876242394a16
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/retu.txt
@@ -0,0 +1,25 @@
+* Device tree bindings for Nokia Retu and Tahvo multi-function device
+
+Retu and Tahvo are a multi-function devices found on Nokia Internet
+Tablets (770, N800 and N810). The Retu chip provides watchdog timer
+and power button control functionalities while Tahvo chip provides
+USB transceiver functionality.
+
+Required properties:
+- compatible: "nokia,retu" or "nokia,tahvo"
+- reg: Specifies the CBUS slave address of the ASIC chip
+- interrupts: The interrupt line the device is connected to
+- interrupt-parent: The parent interrupt controller
+
+Example:
+
+cbus0 {
+ compatible = "i2c-cbus-gpio";
+ ...
+ retu: retu@1 {
+ compatible = "nokia,retu";
+ interrupt-parent = <&gpio4>;
+ interrupts = <12 IRQ_TYPE_EDGE_RISING>;
+ reg = <0x1>;
+ };
+};
--
2.9.3
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name |
| Message-ID | <tDhuV-7tw-13@gated-at.bofh.it> |
| In reply to | #1635414 |
It's not correct to encode the subsystem in the I2C device name, so
drop the -mfd suffix. To maintain bisect-ability, change driver and
platform code / DTS users in the same patch.
Suggested-by: Lee Jones <lee.jones@linaro.org>
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Acked-by: Tony Lindgren <tony@atomide.com>
Reviewed-by: Wolfram Sang <wsa@the-dreams.de>
---
Changes in v6:
- Add Wolfram Sang's Reviewed-by tag.
Changes in v5:
- Add Rob Herring's Acked-by tag.
- Add Aaro Koskinen's Acked-by tag.
- Add Tony Lindgren's Acked-by tag.
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/omap2420-n8x0-common.dtsi | 4 ++--
arch/arm/mach-omap1/board-nokia770.c | 4 ++--
drivers/mfd/retu-mfd.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/omap2420-n8x0-common.dtsi b/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
index 7e5ffc583c90..1b06430c8013 100644
--- a/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
+++ b/arch/arm/boot/dts/omap2420-n8x0-common.dtsi
@@ -15,8 +15,8 @@
>;
#address-cells = <1>;
#size-cells = <0>;
- retu_mfd: retu@1 {
- compatible = "retu-mfd";
+ retu: retu@1 {
+ compatible = "retu";
interrupt-parent = <&gpio4>;
interrupts = <12 IRQ_TYPE_EDGE_RISING>;
reg = <0x1>;
diff --git a/arch/arm/mach-omap1/board-nokia770.c b/arch/arm/mach-omap1/board-nokia770.c
index ee8d9f553db4..06243c0b12d2 100644
--- a/arch/arm/mach-omap1/board-nokia770.c
+++ b/arch/arm/mach-omap1/board-nokia770.c
@@ -233,10 +233,10 @@ static struct platform_device nokia770_cbus_device = {
static struct i2c_board_info nokia770_i2c_board_info_2[] __initdata = {
{
- I2C_BOARD_INFO("retu-mfd", 0x01),
+ I2C_BOARD_INFO("retu", 0x01),
},
{
- I2C_BOARD_INFO("tahvo-mfd", 0x02),
+ I2C_BOARD_INFO("tahvo", 0x02),
},
};
diff --git a/drivers/mfd/retu-mfd.c b/drivers/mfd/retu-mfd.c
index d4c114abeb75..53e1d386d2c0 100644
--- a/drivers/mfd/retu-mfd.c
+++ b/drivers/mfd/retu-mfd.c
@@ -302,8 +302,8 @@ static int retu_remove(struct i2c_client *i2c)
}
static const struct i2c_device_id retu_id[] = {
- { "retu-mfd", 0 },
- { "tahvo-mfd", 0 },
+ { "retu", 0 },
+ { "tahvo", 0 },
{ }
};
MODULE_DEVICE_TABLE(i2c, retu_id);
--
2.9.3
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-04 07:30 +0200 |
| Subject | [PATCH v6 8/8] ARM: ux500: Add vendor prefix to tps61052 node |
| Message-ID | <tDhuW-7tw-17@gated-at.bofh.it> |
| In reply to | #1635414 |
The tps61052 device node doesn't have a vendor prefix
in its compatible string, fix it by adding one.
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Tony Lindgren <tony@atomide.com>
---
Changes in v6: None
Changes in v5:
- Add Rob Herring's Acked-by tag.
- Add Acked-by: Tony Lindgren <tony@atomide.com>'s Acked-by tag.
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/ste-hrefprev60.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/ste-hrefprev60.dtsi b/arch/arm/boot/dts/ste-hrefprev60.dtsi
index 5882a2606ac3..3f14b4df69b4 100644
--- a/arch/arm/boot/dts/ste-hrefprev60.dtsi
+++ b/arch/arm/boot/dts/ste-hrefprev60.dtsi
@@ -30,7 +30,7 @@
i2c@80004000 {
tps61052@33 {
- compatible = "tps61052";
+ compatible = "ti,tps61052";
reg = <0x33>;
};
--
2.9.3
[toc] | [prev] | [next] | [standalone]
| From | Wolfram Sang <wsa@the-dreams.de> |
|---|---|
| Date | 2017-05-04 10:20 +0200 |
| Subject | Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it |
| Message-ID | <tDk9r-S5-1@gated-at.bofh.it> |
| In reply to | #1635414 |
[Multipart message — attachments visible in raw view] — view raw
Javier, thanks for the series. > Most patches can be applied independently, with the exception of patches > 2 to 4 that should be applied in the same tree to keep bisect-ability. I > suggest these to go through the MFD subsystem tree. From my POV, patches 2-5 should be applied to the same tree. Since all I2C related patches have my tag, I assume they will be picked up by MFD. Lee, let me know if you prefer differently.
[toc] | [prev] | [next] | [standalone]
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Date | 2017-05-04 14:00 +0200 |
| Subject | Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it |
| Message-ID | <tDnAn-2VI-33@gated-at.bofh.it> |
| In reply to | #1635469 |
On Thu, 04 May 2017, Wolfram Sang wrote: > thanks for the series. > > > Most patches can be applied independently, with the exception of patches > > 2 to 4 that should be applied in the same tree to keep bisect-ability. I > > suggest these to go through the MFD subsystem tree. > > From my POV, patches 2-5 should be applied to the same tree. Since all > I2C related patches have my tag, I assume they will be picked up by MFD. > Lee, let me know if you prefer differently. I can pick them up, no problem. Can the ARM patches be taking independently? I'm guessing they can since they are separate from one another. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
[toc] | [prev] | [next] | [standalone]
| From | Javier Martinez Canillas <javier@dowhile0.org> |
|---|---|
| Date | 2017-05-05 12:50 +0200 |
| Subject | Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it |
| Message-ID | <tDIYa-yX-11@gated-at.bofh.it> |
| In reply to | #1635671 |
Hello, On Thu, May 4, 2017 at 1:50 PM, Lee Jones <lee.jones@linaro.org> wrote: > On Thu, 04 May 2017, Wolfram Sang wrote: >> thanks for the series. >> >> > Most patches can be applied independently, with the exception of patches >> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I >> > suggest these to go through the MFD subsystem tree. >> >> From my POV, patches 2-5 should be applied to the same tree. Since all Yes, I didn't mention 5 because is just a documentation change. But it would be better if is merged together with 2-4 indeed. >> I2C related patches have my tag, I assume they will be picked up by MFD. >> Lee, let me know if you prefer differently. > > I can pick them up, no problem. Can the ARM patches be taking > independently? I'm guessing they can since they are separate from one > another. > That's corect. The only platform changes that can't be picked independently from MFD are the ones in patch 2, but tha's why I added in the same patch. The OMAP folks (Tony and Aaro) already acked so you can pick it. Best regards, Javier
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web