From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: at91: provide at91_mux_pio3_pin for use in first stage
Date: Mon, 30 Sep 2019 20:34:35 +0200 [thread overview]
Message-ID: <20190930183435.bmdbftvzvsk2nlrg@pengutronix.de> (raw)
In-Reply-To: <20190926093525.12371-1-a.fatoum@pengutronix.de>
On Thu, Sep 26, 2019 at 11:35:24AM +0200, Ahmad Fatoum wrote:
> Low level init code may wish the ability to configure pins, e.g. for low
> level debug UART. The pinctrl-at91 driver already exports an
> at91_mux_pio3_pin function, but that one is only usable after driver
> probe. Instead, provide an at91_mux_pio3_pin function, which can be used
> at all times.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> This is yet unused in the barebox tree.
> But getting it upstream will decouple the sama5d2 second stage support
> from the sama5d3 first stage support, so that both could be sent out
> separately.
> ---
> arch/arm/mach-at91/include/mach/gpio.h | 39 +++++++++++++++++++++++++
> arch/arm/mach-at91/include/mach/iomux.h | 9 +-----
> 2 files changed, 40 insertions(+), 8 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-09-30 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 9:35 Ahmad Fatoum
2019-09-26 9:35 ` [PATCH 2/2] pinctrl: add gpio and pinctrl driver for sama5d2 PIO4 Ahmad Fatoum
2019-09-30 18:34 ` Sascha Hauer [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=20190930183435.bmdbftvzvsk2nlrg@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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