From: yixun.lan@amlogic.com (Yixun Lan)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] pinctrl: meson-g12a: add pinctrl driver support
Date: Thu, 5 Jul 2018 10:52:12 +0800 [thread overview]
Message-ID: <886462fa-1833-a99a-a2fa-5b7dd58341fd@amlogic.com> (raw)
In-Reply-To: <78da7e13-e80b-d714-86d0-7c5f6fc0d9f5@baylibre.com>
HI Neil
On 07/04/18 22:57, Neil Armstrong wrote:
> Hi Yixun,
>
> On 05/07/2018 00:45, Yixun Lan wrote:
>> This patch series try to add pinctrl driver support for
>> the Meson-G12A SoC.
>
> Thanks for submitting these patches.
>
> Can you explicit this patchset with more details on the G12A SoC family ?
> It's relationship with AXG and the differences in term of pinmuxing with the other SoC families ?
>
I thought this was already discussed while we doing pinctrl driver for
Meson-AXG SoC.
Anyway, here it is:
Starting from Meson-AXG SoC, the pinctrl controller block using 4
continues bit to specific pin mux function, while comparing to old
generation SoC which kind of using various length bits for the pin mux
definition. The new design would greatly simplify the software model..
for detail example, one 32bit register can describe 8 pins, and each of
them has 0-7 value to set, start from value 0 to 7.
partition the register into 8 parts:
bit[3:0]
bit[7:4]
bit[11:8]
bit[15:12]
bit[19:16]
bit[23:20]
bit[27:24]
bit[31:28]
for each value:
value == 0, means the pin is GPIO
value = {1, 2, ... 7 } is one of specific PIN function
I could put this info into cover-letter or commit message?
> Why is there a GPIOE bank within the AO controller ?
>
It actually sit in the AO domain, although it's sounds strange from the
naming..
I'm not sure if it's good idea to append a AO suffix? since the
documentation just use the plain GPIOE
> Thanks,
> Neil
>
>>
>> Yixun Lan (3):
>> documentation: Add compatibles for Amlogic Meson G12A pin controllers
>> dt-bindings: pinctrl: meson-g12a: document pin name
>> pinctrl: meson-g12a: add pinctrl driver support
>>
>> .../bindings/pinctrl/meson,pinctrl.txt | 2 +
>> drivers/pinctrl/meson/Kconfig | 6 +
>> drivers/pinctrl/meson/Makefile | 1 +
>> drivers/pinctrl/meson/pinctrl-meson-g12a.c | 1432 +++++++++++++++++
>> include/dt-bindings/gpio/meson-g12a-gpio.h | 114 ++
>> 5 files changed, 1555 insertions(+)
>> create mode 100644 drivers/pinctrl/meson/pinctrl-meson-g12a.c
>> create mode 100644 include/dt-bindings/gpio/meson-g12a-gpio.h
>>
>
> .
>
next prev parent reply other threads:[~2018-07-05 2:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 22:45 Yixun Lan
2018-07-04 14:57 ` Neil Armstrong
2018-07-05 2:52 ` Yixun Lan [this message]
2018-07-09 22:02 ` Martin Blumenstingl
2018-07-10 1:26 ` Yixun Lan
2018-07-04 22:45 ` [PATCH 1/3] documentation: Add compatibles for Amlogic Meson G12A pin controllers Yixun Lan
2018-07-04 22:45 ` [PATCH 2/3] dt-bindings: pinctrl: meson-g12a: document pin name Yixun Lan
2018-07-14 14:47 ` Martin Blumenstingl
2018-07-14 14:53 ` Yixun Lan
2018-07-04 22:45 ` [PATCH 3/3] pinctrl: meson-g12a: add pinctrl driver support Yixun Lan
2018-07-14 15:30 ` Martin Blumenstingl
2018-07-17 6:55 ` Yixun Lan
2018-07-09 13:35 ` [PATCH 0/3] " Linus Walleij
2018-07-09 22:07 ` Martin Blumenstingl
2018-07-10 9:19 ` Yixun Lan
2018-07-14 14:36 ` Martin Blumenstingl
2018-07-14 14:47 ` Yixun Lan
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=886462fa-1833-a99a-a2fa-5b7dd58341fd@amlogic.com \
--to=yixun.lan@amlogic.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 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®