From: shawn.lin@kernel-upstream.org (Shawn Lin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: dts: rockchip: fixes the spi compatible for rk3036
Date: Fri, 20 May 2016 20:35:53 +0800 [thread overview]
Message-ID: <8f662b3b-e359-efdf-72e5-c4f862dd1cf6@kernel-upstream.org> (raw)
In-Reply-To: <1463702182-5188-3-git-send-email-wxt@rock-chips.com>
? 2016/5/20 7:56, Caesar Wang ??:
> That's seem the incorrect string to match the spi driver.
>
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
> Fixes commit f629fcfab2cd
> ("ARM: dts: rockchip: support the spi for rk3036")
>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
> Cc: Heiko Stuebner <heiko@sntech.de>
> Cc: linux-rockchip at lists.infradead.org
>
> ---
>
> Changes in v2: None
>
> arch/arm/boot/dts/rk3036.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/rk3036.dtsi b/arch/arm/boot/dts/rk3036.dtsi
> index d0f4bb7..a30700a 100644
> --- a/arch/arm/boot/dts/rk3036.dtsi
> +++ b/arch/arm/boot/dts/rk3036.dtsi
> @@ -431,7 +431,7 @@
> };
>
> spi: spi at 20074000 {
> - compatible = "rockchip,rockchip-spi";
> + compatible = "rockchip,rk3036-spi";
> reg = <0x20074000 0x1000>;
> interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> clocks =<&cru PCLK_SPI>, <&cru SCLK_SPI>;
>
next prev parent reply other threads:[~2016-05-20 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:56 [PATCH v2 1/3] spi/rockchip: add rk3036/rk3228/rk3368 SoCs for spi document Caesar Wang
2016-05-19 23:56 ` [PATCH v2 2/3] spi/rockchip: add the rk3036/rk3228/rk3368 to match for driver Caesar Wang
2016-05-19 23:56 ` [PATCH v2 3/3] ARM: dts: rockchip: fixes the spi compatible for rk3036 Caesar Wang
2016-05-20 12:35 ` Shawn Lin [this message]
2016-05-20 12:57 ` Caesar Wang
2016-05-20 13:04 ` Shawn Lin
2016-05-20 12:58 ` Heiko Stuebner
2016-05-20 13:09 ` Shawn Lin
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=8f662b3b-e359-efdf-72e5-c4f862dd1cf6@kernel-upstream.org \
--to=shawn.lin@kernel-upstream.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox