From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM64: dts: meson-gx: Prepend GX generic compatible like other nodes
Date: Fri, 10 Mar 2017 16:24:21 -0800 [thread overview]
Message-ID: <m2zigsbqyy.fsf@baylibre.com> (raw)
In-Reply-To: <1489055948-10656-4-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Thu, 9 Mar 2017 11:39:08 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Could use a bit more changelog here (in order to support generic
drivers that work for all GX family, blah, blah...)
Kevin
> ---
> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> index 06d70bf..a010ab9 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> @@ -233,7 +233,7 @@
> };
>
> i2c_A: i2c@8500 {
> - compatible = "amlogic,meson-gxbb-i2c";
> + compatible = "amlogic,meson-gx-i2c", "amlogic,meson-gxbb-i2c";
> reg = <0x0 0x08500 0x0 0x20>;
> interrupts = <GIC_SPI 21 IRQ_TYPE_EDGE_RISING>;
> #address-cells = <1>;
> @@ -279,7 +279,7 @@
> };
>
> i2c_B: i2c@87c0 {
> - compatible = "amlogic,meson-gxbb-i2c";
> + compatible = "amlogic,meson-gx-i2c", "amlogic,meson-gxbb-i2c";
> reg = <0x0 0x087c0 0x0 0x20>;
> interrupts = <GIC_SPI 214 IRQ_TYPE_EDGE_RISING>;
> #address-cells = <1>;
> @@ -288,7 +288,7 @@
> };
>
> i2c_C: i2c@87e0 {
> - compatible = "amlogic,meson-gxbb-i2c";
> + compatible = "amlogic,meson-gx-i2c", "amlogic,meson-gxbb-i2c";
> reg = <0x0 0x087e0 0x0 0x20>;
> interrupts = <GIC_SPI 215 IRQ_TYPE_EDGE_RISING>;
> #address-cells = <1>;
> @@ -297,7 +297,7 @@
> };
>
> spifc: spi@8c80 {
> - compatible = "amlogic,meson-gxbb-spifc";
> + compatible = "amlogic,meson-gx-spifc", "amlogic,meson-gxbb-spifc";
> reg = <0x0 0x08c80 0x0 0x80>;
> #address-cells = <1>;
> #size-cells = <0>;
> @@ -325,7 +325,7 @@
> };
>
> sram: sram@c8000000 {
> - compatible = "amlogic,meson-gxbb-sram", "mmio-sram";
> + compatible = "amlogic,meson-gx-sram", "amlogic,meson-gxbb-sram", "mmio-sram";
> reg = <0x0 0xc8000000 0x0 0x14000>;
>
> #address-cells = <1>;
> @@ -333,12 +333,12 @@
> ranges = <0 0x0 0xc8000000 0x14000>;
>
> cpu_scp_lpri: scp-shmem@0 {
> - compatible = "amlogic,meson-gxbb-scp-shmem";
> + compatible = "amlogic,meson-gx-scp-shmem", "amlogic,meson-gxbb-scp-shmem";
> reg = <0x13000 0x400>;
> };
>
> cpu_scp_hpri: scp-shmem@200 {
> - compatible = "amlogic,meson-gxbb-scp-shmem";
> + compatible = "amlogic,meson-gx-scp-shmem", "amlogic,meson-gxbb-scp-shmem";
> reg = <0x13400 0x400>;
> };
> };
> @@ -390,7 +390,7 @@
> };
>
> ir: ir@580 {
> - compatible = "amlogic,meson-gxbb-ir";
> + compatible = "amlogic,meson-gx-ir", "amlogic,meson-gxbb-ir";
> reg = <0x0 0x00580 0x0 0x40>;
> interrupts = <GIC_SPI 196 IRQ_TYPE_EDGE_RISING>;
> status = "disabled";
prev parent reply other threads:[~2017-03-11 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 10:39 [PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes Neil Armstrong
2017-03-09 10:39 ` [PATCH 1/3] ARM64: dts: meson-gx: Finally move common nodes to GX dtsi Neil Armstrong
2017-03-11 0:23 ` Kevin Hilman
2017-03-13 9:03 ` Neil Armstrong
2017-03-09 10:39 ` [PATCH 2/3] ARM64: dts: meson-gx: empty line cleanup Neil Armstrong
2017-03-09 10:39 ` [PATCH 3/3] ARM64: dts: meson-gx: Prepend GX generic compatible like other nodes Neil Armstrong
2017-03-11 0:24 ` Kevin Hilman [this message]
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=m2zigsbqyy.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox