From: Marek Vasut <marek.vasut@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>, Simon Horman <horms@verge.net.au>
Cc: devicetree@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 9 Jan 2019 13:02:00 +0100 [thread overview]
Message-ID: <34cd1769-f0c9-0c2b-8947-4fceca9a9fb2@gmail.com> (raw)
In-Reply-To: <20190109105754.vvqx6uvsktvxeq7a@ninjato>
On 1/9/19 11:57 AM, Wolfram Sang wrote:
>> [ 3.373714] renesas_sdhi_internal_dmac ee100000.sd: mmc0 base at 0xee100000 max clock rate 200 MHz
>> [ 3.456829] renesas_sdhi_internal_dmac ee120000.sd: mmc1 base at 0xee120000 max clock rate 200 MHz
>
> No mmc2 initialized. That should work regardless of eMMC. Probably
> something wrong in the DT somewhere.
Weird, it worked in next-20181102 with these patches, I just rechecked:
7818a9f06df1 mmc: renesas_sdhi: Whitelist R8A77990 SDHI
a05a906776f8 pinctrl: sh-pfc: r8a77990: Add voltage switch operations
for SDHI
2cc9d3a293e9 pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions
6b8d151613b7 pinctrl: sh-pfc: r8a77990: Add Audio SSI pins, groups and
functions
9167b22938f7 pinctrl: sh-pfc: r8a77990: Add Audio clock pins, groups and
functions
000cc50fc942 arm64: dts: r8a77990-ebisu: Enable HS200 of SDHI3
d3f59bbbf7ce arm64: dts: r8a77990-ebisu: Enable eMMC of SDHI3
5928c59bff8d arm64: dts: r8a77990-ebisu: Enable UHS-I of SDHI0 and SDHI1
dae32a3172b8 arm64: dts: r8a77990-ebisu: Enable SD card of SDHI0 and SDHI1
8feef039c6c6 arm64: dts: r8a77990: Add SDHI device nodes
25e9471b6a27 (tag: next-20181102) Add linux-next specific files for 20181102
I'll let you know once I figure it out.
--
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>, Simon Horman <horms@verge.net.au>
Cc: devicetree@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 9 Jan 2019 13:02:00 +0100 [thread overview]
Message-ID: <34cd1769-f0c9-0c2b-8947-4fceca9a9fb2@gmail.com> (raw)
In-Reply-To: <20190109105754.vvqx6uvsktvxeq7a@ninjato>
On 1/9/19 11:57 AM, Wolfram Sang wrote:
>> [ 3.373714] renesas_sdhi_internal_dmac ee100000.sd: mmc0 base at 0xee100000 max clock rate 200 MHz
>> [ 3.456829] renesas_sdhi_internal_dmac ee120000.sd: mmc1 base at 0xee120000 max clock rate 200 MHz
>
> No mmc2 initialized. That should work regardless of eMMC. Probably
> something wrong in the DT somewhere.
Weird, it worked in next-20181102 with these patches, I just rechecked:
7818a9f06df1 mmc: renesas_sdhi: Whitelist R8A77990 SDHI
a05a906776f8 pinctrl: sh-pfc: r8a77990: Add voltage switch operations
for SDHI
2cc9d3a293e9 pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions
6b8d151613b7 pinctrl: sh-pfc: r8a77990: Add Audio SSI pins, groups and
functions
9167b22938f7 pinctrl: sh-pfc: r8a77990: Add Audio clock pins, groups and
functions
000cc50fc942 arm64: dts: r8a77990-ebisu: Enable HS200 of SDHI3
d3f59bbbf7ce arm64: dts: r8a77990-ebisu: Enable eMMC of SDHI3
5928c59bff8d arm64: dts: r8a77990-ebisu: Enable UHS-I of SDHI0 and SDHI1
dae32a3172b8 arm64: dts: r8a77990-ebisu: Enable SD card of SDHI0 and SDHI1
8feef039c6c6 arm64: dts: r8a77990: Add SDHI device nodes
25e9471b6a27 (tag: next-20181102) Add linux-next specific files for 20181102
I'll let you know once I figure it out.
--
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>, Simon Horman <horms@verge.net.au>
Cc: devicetree@vger.kernel.org,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes
Date: Wed, 9 Jan 2019 13:02:00 +0100 [thread overview]
Message-ID: <34cd1769-f0c9-0c2b-8947-4fceca9a9fb2@gmail.com> (raw)
In-Reply-To: <20190109105754.vvqx6uvsktvxeq7a@ninjato>
On 1/9/19 11:57 AM, Wolfram Sang wrote:
>> [ 3.373714] renesas_sdhi_internal_dmac ee100000.sd: mmc0 base at 0xee100000 max clock rate 200 MHz
>> [ 3.456829] renesas_sdhi_internal_dmac ee120000.sd: mmc1 base at 0xee120000 max clock rate 200 MHz
>
> No mmc2 initialized. That should work regardless of eMMC. Probably
> something wrong in the DT somewhere.
Weird, it worked in next-20181102 with these patches, I just rechecked:
7818a9f06df1 mmc: renesas_sdhi: Whitelist R8A77990 SDHI
a05a906776f8 pinctrl: sh-pfc: r8a77990: Add voltage switch operations
for SDHI
2cc9d3a293e9 pinctrl: sh-pfc: r8a77990: Add SDHI pins, groups and functions
6b8d151613b7 pinctrl: sh-pfc: r8a77990: Add Audio SSI pins, groups and
functions
9167b22938f7 pinctrl: sh-pfc: r8a77990: Add Audio clock pins, groups and
functions
000cc50fc942 arm64: dts: r8a77990-ebisu: Enable HS200 of SDHI3
d3f59bbbf7ce arm64: dts: r8a77990-ebisu: Enable eMMC of SDHI3
5928c59bff8d arm64: dts: r8a77990-ebisu: Enable UHS-I of SDHI0 and SDHI1
dae32a3172b8 arm64: dts: r8a77990-ebisu: Enable SD card of SDHI0 and SDHI1
8feef039c6c6 arm64: dts: r8a77990: Add SDHI device nodes
25e9471b6a27 (tag: next-20181102) Add linux-next specific files for 20181102
I'll let you know once I figure it out.
--
Best regards,
Marek Vasut
_______________________________________________
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:[~2019-01-09 12:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 20:46 [PATCH V3] arm64: dts: r8a77990: ebisu: Add and enable SDHI device nodes Marek Vasut
2018-11-06 20:46 ` Marek Vasut
2018-11-06 20:46 ` Marek Vasut
2018-11-07 8:50 ` Wolfram Sang
2018-11-07 8:50 ` Wolfram Sang
2018-11-07 8:50 ` Wolfram Sang
2018-11-07 10:59 ` Marek Vasut
2018-11-07 10:59 ` Marek Vasut
2018-11-07 10:59 ` Marek Vasut
2018-11-07 13:08 ` Wolfram Sang
2018-11-07 13:08 ` Wolfram Sang
2018-11-07 13:08 ` Wolfram Sang
2018-11-07 13:19 ` Marek Vasut
2018-11-07 13:19 ` Marek Vasut
2018-11-07 13:19 ` Marek Vasut
2018-11-07 19:23 ` Wolfram Sang
2018-11-07 19:23 ` Wolfram Sang
2018-11-07 19:23 ` Wolfram Sang
2018-11-07 20:35 ` Marek Vasut
2018-11-07 20:35 ` Marek Vasut
2018-11-07 20:35 ` Marek Vasut
2018-11-07 11:19 ` Simon Horman
2018-11-07 11:19 ` Simon Horman
2018-11-07 11:19 ` Simon Horman
2018-11-08 12:00 ` Geert Uytterhoeven
2018-11-08 12:00 ` Geert Uytterhoeven
2018-11-08 12:00 ` Geert Uytterhoeven
2018-11-08 13:06 ` Simon Horman
2018-11-08 13:06 ` Simon Horman
2018-11-08 13:06 ` Simon Horman
2018-11-20 10:16 ` Geert Uytterhoeven
2018-11-20 10:16 ` Geert Uytterhoeven
2018-11-20 10:16 ` Geert Uytterhoeven
2018-11-20 23:18 ` Marek Vasut
2018-11-20 23:18 ` Marek Vasut
2018-11-20 23:18 ` Marek Vasut
2018-11-21 8:39 ` Geert Uytterhoeven
2018-11-21 8:39 ` Geert Uytterhoeven
2018-11-21 8:39 ` Geert Uytterhoeven
2019-01-09 10:49 ` Simon Horman
2019-01-09 10:49 ` Simon Horman
2019-01-09 10:49 ` Simon Horman
2019-01-09 10:57 ` Wolfram Sang
2019-01-09 10:57 ` Wolfram Sang
2019-01-09 12:02 ` Marek Vasut [this message]
2019-01-09 12:02 ` Marek Vasut
2019-01-09 12:02 ` Marek Vasut
2019-01-09 12:32 ` Simon Horman
2019-01-09 12:32 ` Simon Horman
2019-01-09 12:32 ` Simon Horman
2019-01-09 12:49 ` Marek Vasut
2019-01-09 12:49 ` Marek Vasut
2019-01-09 12:49 ` Marek Vasut
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=34cd1769-f0c9-0c2b-8947-4fceca9a9fb2@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=takeshi.kihara.df@renesas.com \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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 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.