From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-axg: fix register ranges for SD/eMMC
Date: Tue, 05 Jun 2018 14:56:04 -0700 [thread overview]
Message-ID: <7hlgbskidn.fsf@baylibre.com> (raw)
In-Reply-To: <1528185904.10642.52.camel@baylibre.com> (Jerome Brunet's message of "Tue, 05 Jun 2018 10:05:04 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> On Mon, 2018-06-04 at 15:27 -0700, Kevin Hilman wrote:
>> Based on updated information from Amlogic, correct the register
>> range for the SD/eMMC blocks to the right size.
>>
>> Reported-by: Yixun Lan <yixun.lan@amlogic.com>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>
> Shouldn't we make the same the change on the gx family ?
>
Yes, I was waiting for confirmation from Yixun. Will spin a v2 with GX
included.
Kevin
>> ---
>> Yixun, please test and confirm this still works on AXG boards.
>>
>> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> index fee87737a201..67d7115e4eff 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> @@ -132,7 +132,7 @@
>>
>> sd_emmc_b: sd at 5000 {
>> compatible = "amlogic,meson-axg-mmc";
>> - reg = <0x0 0x5000 0x0 0x2000>;
>> + reg = <0x0 0x5000 0x0 0x800>;
>> interrupts = <GIC_SPI 217 IRQ_TYPE_EDGE_RISING>;
>> status = "disabled";
>> clocks = <&clkc CLKID_SD_EMMC_B>,
>> @@ -144,7 +144,7 @@
>>
>> sd_emmc_c: mmc at 7000 {
>> compatible = "amlogic,meson-axg-mmc";
>> - reg = <0x0 0x7000 0x0 0x2000>;
>> + reg = <0x0 0x7000 0x0 0x800>;
>> interrupts = <GIC_SPI 218 IRQ_TYPE_EDGE_RISING>;
>> status = "disabled";
>> clocks = <&clkc CLKID_SD_EMMC_C>,
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-axg: fix register ranges for SD/eMMC
Date: Tue, 05 Jun 2018 14:56:04 -0700 [thread overview]
Message-ID: <7hlgbskidn.fsf@baylibre.com> (raw)
In-Reply-To: <1528185904.10642.52.camel@baylibre.com> (Jerome Brunet's message of "Tue, 05 Jun 2018 10:05:04 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> On Mon, 2018-06-04 at 15:27 -0700, Kevin Hilman wrote:
>> Based on updated information from Amlogic, correct the register
>> range for the SD/eMMC blocks to the right size.
>>
>> Reported-by: Yixun Lan <yixun.lan@amlogic.com>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>
> Shouldn't we make the same the change on the gx family ?
>
Yes, I was waiting for confirmation from Yixun. Will spin a v2 with GX
included.
Kevin
>> ---
>> Yixun, please test and confirm this still works on AXG boards.
>>
>> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> index fee87737a201..67d7115e4eff 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> @@ -132,7 +132,7 @@
>>
>> sd_emmc_b: sd at 5000 {
>> compatible = "amlogic,meson-axg-mmc";
>> - reg = <0x0 0x5000 0x0 0x2000>;
>> + reg = <0x0 0x5000 0x0 0x800>;
>> interrupts = <GIC_SPI 217 IRQ_TYPE_EDGE_RISING>;
>> status = "disabled";
>> clocks = <&clkc CLKID_SD_EMMC_B>,
>> @@ -144,7 +144,7 @@
>>
>> sd_emmc_c: mmc at 7000 {
>> compatible = "amlogic,meson-axg-mmc";
>> - reg = <0x0 0x7000 0x0 0x2000>;
>> + reg = <0x0 0x7000 0x0 0x800>;
>> interrupts = <GIC_SPI 218 IRQ_TYPE_EDGE_RISING>;
>> status = "disabled";
>> clocks = <&clkc CLKID_SD_EMMC_C>,
next prev parent reply other threads:[~2018-06-05 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 22:27 [PATCH] ARM64: dts: meson-axg: fix register ranges for SD/eMMC Kevin Hilman
2018-06-04 22:27 ` Kevin Hilman
2018-06-05 6:56 ` Yixun Lan
2018-06-05 6:56 ` Yixun Lan
2018-06-05 8:05 ` Jerome Brunet
2018-06-05 8:05 ` Jerome Brunet
2018-06-05 21:56 ` Kevin Hilman [this message]
2018-06-05 21:56 ` Kevin Hilman
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=7hlgbskidn.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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.