Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1593532
| From | Charles Keepax <ckeepax@opensource.wolfsonmicro.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] pinctrl: samsung: Calculate GPIO base for pinctrl_add_gpio_range |
| Date | 2017-03-06 17:50 +0100 |
| Message-ID | <ti3ZE-2qv-23@gated-at.bofh.it> (permalink) |
| References | <tfLXc-2mX-13@gated-at.bofh.it> <tfTL4-7Al-21@gated-at.bofh.it> <thg2R-8pW-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, Mar 04, 2017 at 08:20:11PM +0900, Tomasz Figa wrote:
> Hi Charles,
>
> 2017-03-01 2:04 GMT+09:00 Charles Keepax <ckeepax@opensource.wolfsonmicro.com>:
> > As the pinctrl is now added before the GPIOs are registered we need to
> > manually calculate what the GPIO base will be, otherwise the base for
> > each gpio_range will be set to zero. Fortunately the driver
> > already assigns a GPIO base, in samsung_gpiolib_register, and uses the
> > same calculation it does for the pin_base. Meaning the two will always
> > be the same and allowing us to reuse the pinbase and avoid the issue.
>
> Sorry, I didn't notice before and I don't see the offending patch in ,
> but you should add
>
> Fixes: XXXXXXXXXXXX ("pinctrl: Patch subject")
>
> if you intend to submit this patch separately. Otherwise, maybe this
> can be just squashed?
>
Yeah apologies for that as the original patch hasn't showed up in
the tree yet I couldn't pull a commit ID to add the fixes tag.
Squashing it in is probably the best way to go.
Thanks,
Charles
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v2] pinctrl: samsung: Calculate GPIO base for pinctrl_add_gpio_range Tomasz Figa <tomasz.figa@gmail.com> - 2017-03-04 12:30 +0100 Re: [PATCH v2] pinctrl: samsung: Calculate GPIO base for pinctrl_add_gpio_range Charles Keepax <ckeepax@opensource.wolfsonmicro.com> - 2017-03-06 17:50 +0100
csiph-web