From: Biju Das <biju.das@bp.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH 1/4] gpio: rcar: Enhance gpio-ranges support
Date: Wed, 1 Aug 2018 07:20:20 +0000 [thread overview]
Message-ID: <TYAPR01MB211178DDD3B0C636DACEE539B82D0@TYAPR01MB2111.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdVqSbeGCN-Oq0R2CY5fOoG3ncdc_MtAp6M5+SoW4xXQZw@mail.gmail.com>
Hi Geert,
> Subject: Re: [PATCH 1/4] gpio: rcar: Enhance gpio-ranges support
> A simple way to work around this is to set ngpios to the highest bit number in
> use + 1. But you still need a mechanism to avoid accessing the unused bits in
> the gap between 16 and 27.
>
I will send V2 with following changes
1) Dt binding related to changes for adding optional property " gpio-reserved-ranges" on renesas binding documentation
2) SoC Dtsi with " gpio-ranges = <&pfc 0 96 30>"
3) SoC Dtsi with" gpio-reserved-ranges = <17 10>" which defines unused gpios
4) Handle unused gpios in
a) gpio_rcar_request
b) gpio_rcar_set_multiple
c) gpio_rcar_resume
Regards,
Biju
Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.
next prev parent reply other threads:[~2018-08-01 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 9:51 [PATCH 0/4] Add GPIO and EAVB Pinctrl support Biju Das
2018-07-27 9:51 ` [PATCH 1/4] gpio: rcar: Enhance gpio-ranges support Biju Das
2018-07-30 10:03 ` Geert Uytterhoeven
2018-07-30 10:45 ` Biju Das
2018-08-01 7:20 ` Biju Das [this message]
2018-07-27 9:51 ` [PATCH 2/4] ARM: dts: r8a77470: Add GPIO support Biju Das
2018-07-27 9:51 ` [PATCH 3/4] ARM: dts: iwg23s-sbc: specify EtherAVB PHY IRQ Biju Das
2018-07-30 10:06 ` Geert Uytterhoeven
2018-07-27 9:51 ` [PATCH 4/4] ARM: dts: iwg23s-sbc: Add pinctl support for EtherAVB Biju Das
2018-07-30 15:14 ` Geert Uytterhoeven
2018-07-31 10:26 ` Biju Das
2018-07-31 10:26 ` Biju Das
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=TYAPR01MB211178DDD3B0C636DACEE539B82D0@TYAPR01MB2111.jpnprd01.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.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 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.