From: icenowy@aosc.io
To: maxime.ripard@free-electrons.com
Cc: Linus Walleij <linus.walleij@linaro.org>,
Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH 1/2] pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
Date: Fri, 07 Jul 2017 07:21:19 +0800 [thread overview]
Message-ID: <a55741a065b818d8ff3843471da61c0e@aosc.io> (raw)
In-Reply-To: <20170706204646.3akr57fo6c2ok4wn@flea>
在 2017-07-07 04:46，Maxime Ripard 写道：
> Hi,
>
> On Thu, Jul 06, 2017 at 10:28:21PM +0800, Icenowy Zheng wrote:
>> The PH16 pin has a function with mux id 0x5, which is the DET pin of
>> the
>> "sim" (smart card reader) IP block.
>>
>> This function is missing both in the old A10 and A20 drivers, so it's
>> not found during the merge of these two drivers.
>>
>> Add it to the driver. As we now merged A20 pinctrl driver to the A10
>> one, we need to only fix the A10 driver now.
>>
>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
>
> I'm not sure what you mean there. It's not mentionned in the A10
> datasheet, and neither in the A20. Where did you get that info from?
It's mentioned in all newest datasheets: "A10 Datasheet V1.70.pdf" and
"A20 Datasheet V1.41 20131230.pdf".
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2017-07-06 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:28 [PATCH 0/2] Last step to working Allwinner R40 pinctrl Icenowy Zheng
2017-07-06 14:28 ` [PATCH 1/2] pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver Icenowy Zheng
2017-07-06 20:46 ` Maxime Ripard
2017-07-06 23:21 ` icenowy [this message]
2017-07-10 8:44 ` [linux-sunxi] " Maxime Ripard
2017-07-10 10:23 ` Icenowy Zheng
2017-07-06 14:28 ` [PATCH 2/2] pinctrl: sunxi: add support of R40 to A10 " Icenowy Zheng
2017-07-06 20:50 ` Maxime Ripard
2017-07-06 23:13 ` Icenowy Zheng
2017-07-07 9:18 ` Maxime Ripard
2017-07-07 9:21 ` Icenowy Zheng
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=a55741a065b818d8ff3843471da61c0e@aosc.io \
--to=icenowy@aosc.io \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®