All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v1 1/1] x86/platform: Increase maximum GPIO number for X86_64
Date: Mon, 16 Aug 2021 15:55:59 +0200	[thread overview]
Message-ID: <CAJZ5v0ib7oP5EG2k6_Q0Yiq=_WGu01iGVDmV+QoVRLaxTXZHDw@mail.gmail.com> (raw)
In-Reply-To: <YRppqnAqJ1G+4mva@smile.fi.intel.com>

On Mon, Aug 16, 2021 at 3:35 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Mon, Aug 16, 2021 at 03:25:13PM +0200, Rafael J. Wysocki wrote:
> > On Fri, Aug 6, 2021 at 4:44 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > By default the 512 GPIOs is a maximum on any x86 platform.
> > > With, for example, Intel Tiger Lake-H the SoC based controller
> > > occupies up to 480 pins. This leaves only 32 available for
> > > GPIO expanders or other drivers, like PMIC. Hence, bump the
> > > maximum GPIO number to 1024 for X86_64 and leave 512 for X86_32.
>
> Thanks for review, my answers below.
>
> > > +# The GPIO number here must be sorted by descending number. In case of
> > > +# a multiplatform kernel, we just want the highest value required by the
> > > +# selected platforms.
> > > +config ARCH_NR_GPIO
> > > +       int
> > > +       default 1024 if X86_64
> > > +       default 512 if X86_32
> > > +       default 0
> >
> > Wouldn't
> >
> > default 1024 if X86_64
> > default 512
> >
> > be sufficient?
> >
> > It's either X86_64 or X86_32 anyway AFAICS.
>
> I guess so.
>
> > > +       help
> > > +         Maximum number of GPIOs in the system.
> > > +
> > > +         If unsure, leave the default value.
>
> Btw, what do you think. do we need comment above and help text here? I copied
> these from ARM, but I'm not sure it would be useful on x86 as much.

Both the comment and the help text aren't particularly useful IMO.

The comment is a bit confusing even, because x86 kernels are
multiplatform as a rule.

  reply	other threads:[~2021-08-16 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 14:37 [PATCH v1 1/1] x86/platform: Increase maximum GPIO number for X86_64 Andy Shevchenko
2021-08-11 13:14 ` Linus Walleij
2021-08-11 13:41   ` Andy Shevchenko
2021-08-16 13:25 ` Rafael J. Wysocki
2021-08-16 13:35   ` Andy Shevchenko
2021-08-16 13:55     ` Rafael J. Wysocki [this message]
2021-08-16 14:48       ` Andy Shevchenko

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='CAJZ5v0ib7oP5EG2k6_Q0Yiq=_WGu01iGVDmV+QoVRLaxTXZHDw@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=bp@alien8.de \
    --cc=hdegoede@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.