From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v1, 1/2] gpio: stm32f7: Fix gpio bank hole management
Date: Wed, 9 Jan 2019 21:31:42 -0500 [thread overview]
Message-ID: <20190110023142.GL5463@bill-the-cat> (raw)
In-Reply-To: <1546595706-31360-2-git-send-email-patrice.chotard@st.com>
On Fri, Jan 04, 2019 at 10:55:05AM +0100, Patrice Chotard wrote:
> In case "gpio-ranges" property is not present in device tree,
> use default value for gpio_count and gpio_range.
> This fixes an issue on stm32 F7 and H7 boards where "pinmux status -a"
> command didn't return any pin status due to the fact that both stm32 F7
> and H7 board DT doesn't use the gpio-ranges property.
>
> Fixes: dbf928dd2634a6("gpio: stm32f7: Add gpio bank holes management")
>
> 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/20190109/b92877f3/attachment.sig>
next prev parent reply other threads:[~2019-01-10 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 9:55 [U-Boot] [PATCH v1 0/2] stm32f7 gpio driver fixes Patrice Chotard
2019-01-04 9:55 ` [U-Boot] [PATCH v1 1/2] gpio: stm32f7: Fix gpio bank hole management Patrice Chotard
2019-01-10 2:31 ` Tom Rini [this message]
2019-01-04 9:55 ` [U-Boot] [PATCH v1 2/2] gpio: stm32f7: Fix SPL code size Patrice Chotard
2019-01-10 2:31 ` [U-Boot] [U-Boot,v1,2/2] " Tom Rini
2020-03-31 2:51 ` [U-Boot] [PATCH v1 2/2] " Marek Vasut
2020-03-31 8:12 ` Patrice CHOTARD
2020-03-31 11:22 ` Marek Vasut
2020-03-31 14:10 ` Patrice CHOTARD
2020-03-31 16:07 ` Marek Vasut
2020-03-31 16:08 ` Simon Glass
2020-03-31 16:29 ` Patrick DELAUNAY
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=20190110023142.GL5463@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