From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 5/5] pinctrl: stm32: Update stm32_pinctrl_get_gpio_dev()
Date: Fri, 7 Dec 2018 15:34:24 -0500 [thread overview]
Message-ID: <20181207203424.GT14374@bill-the-cat> (raw)
In-Reply-To: <1543830774-19999-6-git-send-email-patrice.chotard@st.com>
On Mon, Dec 03, 2018 at 10:52:54AM +0100, Patrice Chotard wrote:
> Due to gpio holes management, stm32_pinctrl_get_gpio_dev() must
> be updated.
>
> stm32_pinctrl_get_gpio_dev() returns from a given pin selectors
> the corresponding bank gpio device and the gpio_offset inside this
> gpio bank.
>
> Update also all functions which makes usage of stm32_pinctrl_get_gpio_dev.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181207/e8cd2761/attachment.sig>
prev parent reply other threads:[~2018-12-07 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 9:52 [U-Boot] [PATCH 0/5] Update STM32 gpio and pinctrl drivers Patrice Chotard
2018-12-03 9:52 ` [U-Boot] [PATCH 1/5] pinctrl: stm32: Move gpio_dev list filling outside probe() Patrice Chotard
2018-12-07 20:34 ` [U-Boot] [U-Boot, " Tom Rini
2018-12-03 9:52 ` [U-Boot] [PATCH 2/5] gpio: stm32f7: Add gpio bank holes management Patrice Chotard
2018-12-07 20:34 ` [U-Boot] [U-Boot, " Tom Rini
2018-12-03 9:52 ` [U-Boot] [PATCH 3/5] gpio: stm32f7: Move STM32_GPIOS_PER_BANK into gpio.h Patrice Chotard
2018-12-07 20:34 ` [U-Boot] [U-Boot, " Tom Rini
2018-12-03 9:52 ` [U-Boot] [PATCH 4/5] gpio: stm32f7: Remove CONFIG_CLK flag Patrice Chotard
2018-12-07 20:34 ` [U-Boot] [U-Boot,4/5] " Tom Rini
2018-12-03 9:52 ` [U-Boot] [PATCH 5/5] pinctrl: stm32: Update stm32_pinctrl_get_gpio_dev() Patrice Chotard
2018-12-07 20:34 ` Tom Rini [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=20181207203424.GT14374@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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