From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC V2] devicetree: Dialog Semiconductor consolidate existing vendor prefixes to standardise on 'dlg'
Date: Tue, 22 Jul 2014 08:09:27 +0100 [thread overview]
Message-ID: <20140722070927.GC28529@lee--X1> (raw)
In-Reply-To: <201407151520.s6FFKcjB009745@swsrvapps-01.diasemi.com>
On Tue, 15 Jul 2014, Opensource [Steve Twiss] wrote:
> From: Opensource [Steve Twiss] <stwiss.opensource@diasemi.com>
>
> This patch series updates the device tree vendor prefix for
> Dialog Semiconductor.
>
> Various methods are currently used throughout the kernel: 'diasemi',
> 'dialog' and 'dlg'. Others have also been suggested.
>
> This patch set aims to consolidate the usage of the vendor prefix to
> use a common standard. The prefix 'dlg' is used.
>
> Here is my working for justifying this change:
>
> ./arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi
> Has the following entry:
> compatible = "dialog,da9063";
> However the DA9063 driver does not support device tree yet so
> it would be safe to rename this.
>
> ./arch/arm/boot/dts/imx53-smd.dts
> Has the following entry:
> compatible = "dialog,da9053", "dialog,da9052";
> However, the existing driver files for DA9053 define a different
> compatible string with the "dlg" prefix. See the entries below.
> None of these would have allowed the "dialog" prefix.
> { .compatible = "dlg,da9052", .data = &da9052_i2c_id[0] },
> { .compatible = "dlg,da9053-aa", .data = &da9052_i2c_id[1] },
> { .compatible = "dlg,da9053-ba", .data = &da9052_i2c_id[2] },
> { .compatible = "dlg,da9053-bb", .data = &da9052_i2c_id[3] },
> { .compatible = "dlg,da9053-bc", .data = &da9052_i2c_id[4] },
> In this particular case the change for DA9053 did not match up
> with the expected compatibility strings and therefore I have
> retained the more general "dlg,da9053" because I do not know
> which silicon variant (-aa, -ba, -bb, or -bc) is the correct
> one to use.
>
> ./devicetree/bindings/i2c/trivial-devices.txt
> Has the following entry:
> dialog,da9053 DA9053: flexible system level PMIC with multicore support
> Instead of depreciating this "dialog" line I am just replacing it
> with a "dlg" because the existing driver DA9053 does not support
> the dialog keyword.
>
> ./drivers/mfd/da9055-core.c
> Has the following entries for the mfd cells
> .of_compatible = "dialog,da9055-gpio", etc...
> In this case, the driver does not actually pass in any platform data
> to any of the mfd cells and so they are not actually used
> yet in the driver. Nobody else references this information.
>
> ./devicetree/bindings/regulator/da9210.txt
> Has the following two entries in the binding file:
> - compatible: must be "diasemi,da9210"
> compatible = "diasemi,da9210";
> However the DA9210 driver does not support device tree.
>
> ./arch/arm/boot/dts/r8a7790-lager.dts
> ./arch/arm/boot/dts/r8a7791-koelsch.dts
> These two files have the following entries:
> compatible = "diasemi,da9210";
> These both reference the "diasemi,da9210" but the device
> driver does not support device tree
>
> The remaining files in the kernel I have found correctly references
> the driver files compatibility information and so did not need to
> be changed.
>
> ./devicetree/bindings/mfd/da9052-i2c.txt
> - compatible : Should be "dlg,da9052", "dlg,da9053-aa",
> "dlg,da9053-ab", or "dlg,da9053-bb"
>
> ./devicetree/bindings/mfd/da9055.txt
> compatible = "dlg,da9055-pmic";
>
> ./arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi
> compatible = "dlg,da9053-aa", "dlg,da9052";
>
> ./arch/arm/boot/dts/imx53-qsb.dts
> compatible = "dlg,da9053-aa", "dlg,da9052";
>
> ./devicetree/bindings/sound/da9055.txt
> - compatible: "dlg,da9055-codec"
> compatible = "dlg,da9055-codec";
>
>
> Signed-off-by: Opensource [Steve Twiss] <stwiss.opensource@diasemi.com>
> ---
> Checks performed with linux-next/next-20140715/scripts/checkpatch.pl
> trivial-devices.txt total: 0 errors, 0 warnings, 89 lines checked
> da9210.txt total: 0 errors, 0 warnings, 21 lines checked
> vendor-prefixes.txt total: 0 errors, 0 warnings, 149 lines checked
> imx53-smd.dts total: 0 errors, 2 warnings, 279 lines checked
> imx6qdl-phytec-pfla02.dtsi total: 0 errors, 2 warnings, 357 lines checked
> r8a7790-lager.dts total: 0 errors, 3 warnings, 403 lines checked
> r8a7791-koelsch.dts total: 0 errors, 4 warnings, 461 lines checked
> da9055-core.c total: 0 errors, 0 warnings, 428 lines checked
>
> This e-mail is in response to the previous threads here:
> https://lkml.org/lkml/2014/6/11/262
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/341358
>
> Changes since RFC V1
> - addition of changes to DTS files referencing "diasemi,da9210"
> arch/arm/boot/dts/r8a7790-lager.dts
> arch/arm/boot/dts/r8a7791-koelsch.dts
>
> This RFC V2 does not answer the response to RFC V1 from Mark Brown:
> http://www.spinics.net/lists/arm-kernel/msg347615.html
>
> This patch applies against linux-next and next-20140715
>
> Regards,
> Steve Twiss, Dialog Semiconductor Ltd.
>
>
>
> .../devicetree/bindings/i2c/trivial-devices.txt | 2 +-
> .../devicetree/bindings/regulator/da9210.txt | 4 ++--
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm/boot/dts/imx53-smd.dts | 2 +-
> arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 2 +-
> arch/arm/boot/dts/r8a7790-lager.dts | 2 +-
> arch/arm/boot/dts/r8a7791-koelsch.dts | 2 +-
> drivers/mfd/da9055-core.c | 26 ++++++++++----------
For the MFD changes:
Acked-by: Lee Jones <lee.jones@linaro.org>
Which tree is this patch going into? Do you want me to take it and
supply an IB for the other Maintainers to pull from?
> 8 files changed, 21 insertions(+), 20 deletions(-)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
LINUX SH <linux-sh@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Mark Brown <broonie@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Shawn Guo <shawn.guo@freescale.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Florian Vaussard <florian.vaussard@epfl.ch>,
DEVICE TREE <devicetree@vger.kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Arnaud Ebalard <arno@natisbad.org>,
Rob Herring <robh+dt@kernel.org>,
LINUX ARM KERNEL <linux-arm-kernel@lists.infradead.org>,
Martin Fuzzey <mfuzzey@parkeon.com>,
Support Opensource <support.opensource@diasemi.com>,
LINUX KERNEL <linux-kernel@vger.kernel.or>
Subject: Re: [RFC V2] devicetree: Dialog Semiconductor consolidate existing vendor prefixes to standardise on 'dlg'
Date: Tue, 22 Jul 2014 08:09:27 +0100 [thread overview]
Message-ID: <20140722070927.GC28529@lee--X1> (raw)
In-Reply-To: <201407151520.s6FFKcjB009745@swsrvapps-01.diasemi.com>
On Tue, 15 Jul 2014, Opensource [Steve Twiss] wrote:
> From: Opensource [Steve Twiss] <stwiss.opensource@diasemi.com>
>
> This patch series updates the device tree vendor prefix for
> Dialog Semiconductor.
>
> Various methods are currently used throughout the kernel: 'diasemi',
> 'dialog' and 'dlg'. Others have also been suggested.
>
> This patch set aims to consolidate the usage of the vendor prefix to
> use a common standard. The prefix 'dlg' is used.
>
> Here is my working for justifying this change:
>
> ./arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi
> Has the following entry:
> compatible = "dialog,da9063";
> However the DA9063 driver does not support device tree yet so
> it would be safe to rename this.
>
> ./arch/arm/boot/dts/imx53-smd.dts
> Has the following entry:
> compatible = "dialog,da9053", "dialog,da9052";
> However, the existing driver files for DA9053 define a different
> compatible string with the "dlg" prefix. See the entries below.
> None of these would have allowed the "dialog" prefix.
> { .compatible = "dlg,da9052", .data = &da9052_i2c_id[0] },
> { .compatible = "dlg,da9053-aa", .data = &da9052_i2c_id[1] },
> { .compatible = "dlg,da9053-ba", .data = &da9052_i2c_id[2] },
> { .compatible = "dlg,da9053-bb", .data = &da9052_i2c_id[3] },
> { .compatible = "dlg,da9053-bc", .data = &da9052_i2c_id[4] },
> In this particular case the change for DA9053 did not match up
> with the expected compatibility strings and therefore I have
> retained the more general "dlg,da9053" because I do not know
> which silicon variant (-aa, -ba, -bb, or -bc) is the correct
> one to use.
>
> ./devicetree/bindings/i2c/trivial-devices.txt
> Has the following entry:
> dialog,da9053 DA9053: flexible system level PMIC with multicore support
> Instead of depreciating this "dialog" line I am just replacing it
> with a "dlg" because the existing driver DA9053 does not support
> the dialog keyword.
>
> ./drivers/mfd/da9055-core.c
> Has the following entries for the mfd cells
> .of_compatible = "dialog,da9055-gpio", etc...
> In this case, the driver does not actually pass in any platform data
> to any of the mfd cells and so they are not actually used
> yet in the driver. Nobody else references this information.
>
> ./devicetree/bindings/regulator/da9210.txt
> Has the following two entries in the binding file:
> - compatible: must be "diasemi,da9210"
> compatible = "diasemi,da9210";
> However the DA9210 driver does not support device tree.
>
> ./arch/arm/boot/dts/r8a7790-lager.dts
> ./arch/arm/boot/dts/r8a7791-koelsch.dts
> These two files have the following entries:
> compatible = "diasemi,da9210";
> These both reference the "diasemi,da9210" but the device
> driver does not support device tree
>
> The remaining files in the kernel I have found correctly references
> the driver files compatibility information and so did not need to
> be changed.
>
> ./devicetree/bindings/mfd/da9052-i2c.txt
> - compatible : Should be "dlg,da9052", "dlg,da9053-aa",
> "dlg,da9053-ab", or "dlg,da9053-bb"
>
> ./devicetree/bindings/mfd/da9055.txt
> compatible = "dlg,da9055-pmic";
>
> ./arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi
> compatible = "dlg,da9053-aa", "dlg,da9052";
>
> ./arch/arm/boot/dts/imx53-qsb.dts
> compatible = "dlg,da9053-aa", "dlg,da9052";
>
> ./devicetree/bindings/sound/da9055.txt
> - compatible: "dlg,da9055-codec"
> compatible = "dlg,da9055-codec";
>
>
> Signed-off-by: Opensource [Steve Twiss] <stwiss.opensource@diasemi.com>
> ---
> Checks performed with linux-next/next-20140715/scripts/checkpatch.pl
> trivial-devices.txt total: 0 errors, 0 warnings, 89 lines checked
> da9210.txt total: 0 errors, 0 warnings, 21 lines checked
> vendor-prefixes.txt total: 0 errors, 0 warnings, 149 lines checked
> imx53-smd.dts total: 0 errors, 2 warnings, 279 lines checked
> imx6qdl-phytec-pfla02.dtsi total: 0 errors, 2 warnings, 357 lines checked
> r8a7790-lager.dts total: 0 errors, 3 warnings, 403 lines checked
> r8a7791-koelsch.dts total: 0 errors, 4 warnings, 461 lines checked
> da9055-core.c total: 0 errors, 0 warnings, 428 lines checked
>
> This e-mail is in response to the previous threads here:
> https://lkml.org/lkml/2014/6/11/262
> http://comments.gmane.org/gmane.linux.ports.arm.kernel/341358
>
> Changes since RFC V1
> - addition of changes to DTS files referencing "diasemi,da9210"
> arch/arm/boot/dts/r8a7790-lager.dts
> arch/arm/boot/dts/r8a7791-koelsch.dts
>
> This RFC V2 does not answer the response to RFC V1 from Mark Brown:
> http://www.spinics.net/lists/arm-kernel/msg347615.html
>
> This patch applies against linux-next and next-20140715
>
> Regards,
> Steve Twiss, Dialog Semiconductor Ltd.
>
>
>
> .../devicetree/bindings/i2c/trivial-devices.txt | 2 +-
> .../devicetree/bindings/regulator/da9210.txt | 4 ++--
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm/boot/dts/imx53-smd.dts | 2 +-
> arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 2 +-
> arch/arm/boot/dts/r8a7790-lager.dts | 2 +-
> arch/arm/boot/dts/r8a7791-koelsch.dts | 2 +-
> drivers/mfd/da9055-core.c | 26 ++++++++++----------
For the MFD changes:
Acked-by: Lee Jones <lee.jones@linaro.org>
Which tree is this patch going into? Do you want me to take it and
supply an IB for the other Maintainers to pull from?
> 8 files changed, 21 insertions(+), 20 deletions(-)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-07-22 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 15:03 [RFC V2] devicetree: Dialog Semiconductor consolidate existing vendor prefixes to standardise on 'dlg' Opensource [Steve Twiss]
2014-07-15 15:03 ` Opensource [Steve Twiss]
2014-07-21 14:40 ` Opensource [Steve Twiss]
2014-07-21 14:40 ` Opensource [Steve Twiss]
2014-07-21 15:43 ` Rob Herring
2014-07-21 15:43 ` Rob Herring
2014-07-22 1:38 ` Shawn Guo
2014-07-22 1:38 ` Shawn Guo
2014-07-22 7:09 ` Lee Jones [this message]
2014-07-22 7:09 ` Lee Jones
2014-07-23 9:17 ` Opensource [Steve Twiss]
2014-07-23 9:17 ` Opensource [Steve Twiss]
2014-07-23 10:12 ` Lee Jones
2014-07-23 10:12 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140722070927.GC28529@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.