mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/7] gpio: allow for arch-specific ARCH_NR_GPIOS > 256
Date: Mon, 15 Jul 2019 08:42:13 +0200	[thread overview]
Message-ID: <20190715064213.n7e3stajq7wcqpoh@pengutronix.de> (raw)
In-Reply-To: <20190710201112.9086-1-a.fatoum@pengutronix.de>

On Wed, Jul 10, 2019 at 10:11:06PM +0200, Ahmad Fatoum wrote:
> Some architectures have non-contiguous GPIO ranges where some GPIOs can
> have identifiers exceeding the hardcoded ARCH_NR_GPIOs of 256.
> 
> One such example is the STM32MP, whose gpioz controller has identifiers
> that go up to ('Z' - 'A' + 1) * 0x10 - 1 = 415.
> Instead of increasing the array size for all architectures or doing
> some sort of packing, allow architecture to define their own overriding
> CONFIG_ARCH_NR_GPIO like the kernel does.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  include/gpio.h | 4 ++++
>  1 file changed, 4 insertions(+)

Applied 1-4, 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

      parent reply	other threads:[~2019-07-15  6:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 20:11 Ahmad Fatoum
2019-07-10 20:11 ` [PATCH 2/7] ARM: stm32mp: set CONFIG_ARCH_NR_GPIO = (26 * 16) Ahmad Fatoum
2019-07-10 20:11 ` [PATCH 3/7] ARM: dts: stm32mp157c: correct gpioz id Ahmad Fatoum
2019-07-10 20:11 ` [PATCH 4/7] reset: add reset controller driver for STM32 RCC Ahmad Fatoum
2019-07-10 21:28   ` [PATCH] fixup! " Ahmad Fatoum
2019-07-10 20:11 ` [PATCH 5/7] i2c: add stm32f7 I2C adapter driver Ahmad Fatoum
2019-07-12  5:09   ` Sascha Hauer
2019-07-10 20:11 ` [PATCH 6/7] mfd: add support for STPMIC1 Ahmad Fatoum
2019-07-10 20:11 ` [PATCH 7/7] watchdog: add support for STPMIC1 integrated watchdog Ahmad Fatoum
2019-07-15  6:42 ` 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=20190715064213.n7e3stajq7wcqpoh@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