From: Xingyu Chen <xingyu.chen@amlogic.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org
Cc: jbrunet@baylibre.com, khilman@baylibre.com, carlo@caione.org,
martin.blumenstingl@googlemail.com, robh@kernel.org,
jianxin.pan@amlogic.com, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: meson: fix G12A ao pull registers base address
Date: Tue, 4 Dec 2018 10:05:00 +0800 [thread overview]
Message-ID: <b3ccafc4-0bd2-273b-b0b2-96bbdeb9ee1b@amlogic.com> (raw)
In-Reply-To: <a240773f-7b05-d950-e5e9-23d7983c7f35@baylibre.com>
On 2018/12/3 18:27, Neil Armstrong wrote:
> Hi Xingyu,
>
>
> On 03/12/2018 04:05, Xingyu Chen wrote:
>> Since Meson G12A SoC, Introduce new ao registers AO_RTI_PULL_UP_EN_REG
>> and AO_GPIO_O.
>>
>> These bits of controlling output level are remapped to the new register
>> AO_GPIO_O, and the AO_GPIO_O_EN_N support only controlling output enable.
>>
>> These bits of controlling pull enable are remapped to the new register
>> AO_RTI_PULL_UP_EN_REG, and the AO_RTI_PULL_UP_REG support only controlling
>> pull type(up/down).
>>
>> The new layout of ao gpio/pull registers is as follows:
>> - AO_GPIO_O_EN_N [offset: 0x9 << 2]
>> - AO_GPIO_I [offset: 0xa << 2]
>> - AO_RTI_PULL_UP_REG [offset: 0xb << 2]
>> - AO_RTI_PULL_UP_EN_REG [offset: 0xc << 2]
>> - AO_GPIO_O [offset: 0xd << 2]
>>
>> From above, we can see ao GPIO registers region has been separated by the
>> ao pull registers. In order to ensure the continuity of the region on
>> software, the ao GPIO and ao pull registers use the same base address, but
>> can be identified by the offset.
>>
>> Fixes: 29ae0952e85f ("pinctrl: meson-g12a: add pinctrl driver support")
>> Signed-off-by: Xingyu Chen <xingyu.chen@amlogic.com>
>> Signed-off-by: Jianxin Pan <jianxin.pan@amlogic.com>
>> ---
>> drivers/pinctrl/meson/pinctrl-meson.c | 22 ++++++++++++----------
>> 1 file changed, 12 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/pinctrl/meson/pinctrl-meson.c b/drivers/pinctrl/meson/pinctrl-meson.c
>> index 53d449076dee..7ff40cd7a0cb 100644
>> --- a/drivers/pinctrl/meson/pinctrl-meson.c
>> +++ b/drivers/pinctrl/meson/pinctrl-meson.c
>> @@ -31,6 +31,9 @@
>> * In some cases the register ranges for pull enable and pull
>> * direction are the same and thus there are only 3 register ranges.
>> *
>> + * Since Meson G12A SoC, the ao register ranges for gpio, pull enable
>> + * and pull direction are the same, so there are only 2 register ranges.
>> + *
>> * For the pull and GPIO configuration every bank uses a contiguous
>> * set of bits in the register sets described above; the same register
>> * can be shared by more banks with different offsets.
>> @@ -487,23 +490,22 @@ static int meson_pinctrl_parse_dt(struct meson_pinctrl *pc,
>> return PTR_ERR(pc->reg_mux);
>> }
>>
>> - pc->reg_pull = meson_map_resource(pc, gpio_np, "pull");
>> - if (IS_ERR(pc->reg_pull)) {
>> - dev_err(pc->dev, "pull registers not found\n");
>> - return PTR_ERR(pc->reg_pull);
>> + pc->reg_gpio = meson_map_resource(pc, gpio_np, "gpio");
>> + if (IS_ERR(pc->reg_gpio)) {
>> + dev_err(pc->dev, "gpio registers not found\n");
>> + return PTR_ERR(pc->reg_gpio);
>> }
>>
>> + pc->reg_pull = meson_map_resource(pc, gpio_np, "pull");
>> + /* Use gpio region if pull one is not present */
>> + if (IS_ERR(pc->reg_pull))
>> + pc->reg_pull = pc->reg_gpio;
>> +
>> pc->reg_pullen = meson_map_resource(pc, gpio_np, "pull-enable");
>> /* Use pull region if pull-enable one is not present */
>> if (IS_ERR(pc->reg_pullen))
>> pc->reg_pullen = pc->reg_pull;
>>
>> - pc->reg_gpio = meson_map_resource(pc, gpio_np, "gpio");
>> - if (IS_ERR(pc->reg_gpio)) {
>> - dev_err(pc->dev, "gpio registers not found\n");
>> - return PTR_ERR(pc->reg_gpio);
>> - }
>> -
>> return 0;
>> }
>>
>>
> Doesn't it need an update of the bindings ?
>
> Neil
>
Thanks, I will update it in next patch
> .
>
prev parent reply other threads:[~2018-12-04 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 3:05 [PATCH] pinctrl: meson: fix G12A ao pull registers base address Xingyu Chen
2018-12-03 10:27 ` Neil Armstrong
2018-12-03 10:36 ` Jerome Brunet
2018-12-04 2:10 ` Xingyu Chen
2018-12-04 2:05 ` Xingyu Chen [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=b3ccafc4-0bd2-273b-b0b2-96bbdeb9ee1b@amlogic.com \
--to=xingyu.chen@amlogic.com \
--cc=carlo@caione.org \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.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).