From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org,
Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: Re: (subset) [PATCH] ARM: at91: xload: use pin_to_mask for peripheral pin configuration
Date: Wed, 18 Jun 2025 12:13:15 +0200 [thread overview]
Message-ID: <175024159556.1454277.10424590893584056759.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250618063552.23777-5-eagle.alexander923@gmail.com>
On Wed, 18 Jun 2025 09:35:52 +0300, Alexander Shiyan wrote:
> The patch replaces the use of BIT(*pin) with pin_to_mask(*pin) when
> configuring peripheral pins for both SDHCI and QSPI boot modes.
>
>
Applied, thanks!
[1/1] ARM: at91: xload: use pin_to_mask for peripheral pin configuration
https://git.pengutronix.de/cgit/barebox/commit/?id=c74dd656505f (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next prev parent reply other threads:[~2025-06-18 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 6:35 [PATCH] ARM: at91: clock: remove unused SAMA5D2/SAMA5D3 support from legacy clock driver Alexander Shiyan
2025-06-18 6:35 ` [PATCH] ARM: at91: sam9x5ek: enable missing DT and clock options for devicetree boot Alexander Shiyan
2025-06-18 10:13 ` Sascha Hauer
2025-06-18 6:35 ` [PATCH] ARM: at91: setup: improve address handling for DBGU and CHIPID detection Alexander Shiyan
2025-06-18 10:13 ` Sascha Hauer
2025-06-18 6:35 ` [PATCH] ARM: at91: setup: refactor SoC subtype detection with switch statements Alexander Shiyan
2025-06-18 10:13 ` Sascha Hauer
2025-06-18 6:35 ` [PATCH] ARM: at91: xload: use pin_to_mask for peripheral pin configuration Alexander Shiyan
2025-06-18 10:13 ` Sascha Hauer
2025-06-18 10:13 ` Sascha Hauer [this message]
2025-06-18 10:13 ` (subset) [PATCH] ARM: at91: clock: remove unused SAMA5D2/SAMA5D3 support from legacy clock driver Sascha Hauer
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=175024159556.1454277.10424590893584056759.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
/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