From: "Christian Daudt" <csd@broadcom.com>
To: "Christian Daudt" <csd@broadcom.com>
Cc: "Lee Jones" <lee.jones@linaro.org>,
"Alex Elder" <elder@linaro.org>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ian.campbell@citrix.com>,
"Russell King" <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: align sdio numbers to HW definition
Date: Mon, 19 Aug 2013 16:59:36 -0700 [thread overview]
Message-ID: <5212B168.909@broadcom.com> (raw)
In-Reply-To: <1375988874-11303-1-git-send-email-csd@broadcom.com>
On 13-08-08 12:07 PM, Christian Daudt wrote:
> Clean up the sdio numbering to be 1-base as defined in HW spec,
> instead of the current 0-base
>
> Reviewed-by: Alex Elder <elder@linaro.org>
> Signed-off-by: Christian Daudt <csd@broadcom.com>
>
> diff --git a/arch/arm/boot/dts/bcm11351-brt.dts b/arch/arm/boot/dts/bcm11351-brt.dts
> index 67ec524..647a78c 100644
> --- a/arch/arm/boot/dts/bcm11351-brt.dts
> +++ b/arch/arm/boot/dts/bcm11351-brt.dts
> @@ -27,18 +27,18 @@
> status = "okay";
> };
>
> - sdio0: sdio@0x3f180000 {
> + sdio1: sdio@3f180000 {
> max-frequency = <48000000>;
> status = "okay";
> };
>
> - sdio1: sdio@0x3f190000 {
> + sdio2: sdio@3f190000 {
> non-removable;
> max-frequency = <48000000>;
> status = "okay";
> };
>
> - sdio3: sdio@0x3f1b0000 {
> + sdio4: sdio@3f1b0000 {
> max-frequency = <48000000>;
> status = "okay";
> };
> diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arch/arm/boot/dts/bcm11351.dtsi
> index 8f094ba..d34e49db 100644
> --- a/arch/arm/boot/dts/bcm11351.dtsi
> +++ b/arch/arm/boot/dts/bcm11351.dtsi
> @@ -68,28 +68,28 @@
> clock-frequency = <32768>;
> };
>
> - sdio0: sdio@0x3f180000 {
> + sdio1: sdio@3f180000 {
> compatible = "bcm,kona-sdhci";
> reg = <0x3f180000 0x10000>;
> interrupts = <0x0 77 0x4>;
> status = "disabled";
> };
>
> - sdio1: sdio@0x3f190000 {
> + sdio2: sdio@3f190000 {
> compatible = "bcm,kona-sdhci";
> reg = <0x3f190000 0x10000>;
> interrupts = <0x0 76 0x4>;
> status = "disabled";
> };
>
> - sdio2: sdio@0x3f1a0000 {
> + sdio3: sdio@3f1a0000 {
> compatible = "bcm,kona-sdhci";
> reg = <0x3f1a0000 0x10000>;
> interrupts = <0x0 74 0x4>;
> status = "disabled";
> };
>
> - sdio3: sdio@0x3f1b0000 {
> + sdio4: sdio@3f1b0000 {
> compatible = "bcm,kona-sdhci";
> reg = <0x3f1b0000 0x10000>;
> interrupts = <0x0 73 0x4>;
applied to bcm/for-3.12/dt
thanks,
csd
prev parent reply other threads:[~2013-08-19 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 19:07 [PATCH 1/2] ARM: dts: align sdio numbers to HW definition Christian Daudt
2013-08-08 19:07 ` [PATCH 2/2] ARM: dts: add sdio blocks to bcm28155-ap board Christian Daudt
2013-08-19 23:59 ` Christian Daudt
2013-08-19 23:59 ` Christian Daudt [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=5212B168.909@broadcom.com \
--to=csd@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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