From: Shawn Lin <shawn.lin@rock-chips.com>
To: Caesar Wang <caesar.upstream@gmail.com>,
Heiko Stuebner <heiko@sntech.de>
Cc: shawn.lin@rock-chips.com, Jaehoon Chung <jh80.chung@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: dw_mmc-rockchip: add pinctrl support
Date: Wed, 20 Jan 2016 08:54:52 +0800 [thread overview]
Message-ID: <569EDADC.4020302@rock-chips.com> (raw)
In-Reply-To: <569E21C3.2080606@gmail.com>
On 2016/1/19 19:45, Caesar Wang wrote:
>
> 在 2016年01月19日 19:07, Shawn Lin 写道:
>> On 2016/1/19 18:07, Heiko Stuebner wrote:
>>> Hi Shawn,
>>>
>>> Am Dienstag, 19. Januar 2016, 17:52:45 schrieb Shawn Lin:
>>>> We find rk3368 fail to enumerate sd card since
>>>> the default state is gpio function. Meahwhile, lots of
>>>> rockchip platform dts file assign pinctrl to dw_mmc but actually
>>>> dw_mmc never use it. Fortunately, those platforms' default io
>>>> state is sdmmc function, but no always right for all.
>>>>
>>>> Cc: Heiko Stuebner <heiko@sntech.de>
>>>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>>>
>>> I do believe any issue you see, must come from somewhere else,
>>> because the
>>> driver-core does in drivers/base/dd.c really_probe():
>>> pinctrl_bind_pins()
>>
>> yes, pinctrl_bind_pins does turn pinctrl state. But I try debug a little
>> more and seems somewhere else switch the state before dw_mmc probe.
>> Now I *guess* that may relate to our ATF or MCU firmware since
>> rk3368's sdmmc io can also be used as mcu_jtag for system debug. I
>> need to double check that point, thanks.
>>
>
> Yep, maybe that's related to the firmware setting.
> I guess you can repro this issue on RK3368 platform.
> At least until now, the RK3036, RK3288....that's work well.
>
Hi Caesar,
Then I check this issue with MCU firmware guys and it does force
pin setting into mcu_jtag function。 Now I can see only 3368 apply
MCU firmware, right? Another thing, seems old version firmware didn't
break the sdmmc function.
I think it's better to slove this problem in firmware side,
not Linux. So, abandon this patch!
>
>> Hi Caesar,
>> does your patch able to consider adding SDMMC/CPU_JTAG/MCU_JTAG
>> managment for rk3368 as well?
>>
>
> That's no related, I will add the sdmmc node and check it on tomorrow
> if the time can be availabled.
>
>
>>> which in turn already does the needed pinctrl state handling.
>>>
>>> So that default-state should be set up even before the dwmmc probe
>>> function
>>> is called.
>>>
>>> The sharing between sdmmc and uart2 pins is the same on the rk3036
>>> and so
>>> far Caesar seems to have been able to switch the pin-state to sdmmc
>>> without
>>> touching the dw_mmc driver itself.
>>>
>
> Yep, that's working on rk3036 kylin board.
>
>
> ---
> Thanks,
> Caesar
>
>
>
--
Best Regards
Shawn Lin
prev parent reply other threads:[~2016-01-20 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 9:52 [PATCH] mmc: dw_mmc-rockchip: add pinctrl support Shawn Lin
2016-01-19 10:07 ` Heiko Stuebner
2016-01-19 11:07 ` Shawn Lin
2016-01-19 11:45 ` Caesar Wang
2016-01-20 0:54 ` Shawn Lin [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=569EDADC.4020302@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=caesar.upstream@gmail.com \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).