From: Raag Jadav <raag.jadav@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kees@kernel.org, broonie@kernel.org, gregkh@linuxfoundation.org,
arnd@arndb.de, hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
linus.walleij@linaro.org, brgl@bgdev.pl,
platform-driver-x86@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mod_devicetable: Bump auxiliary_device_id name size
Date: Thu, 6 Nov 2025 08:58:44 +0100 [thread overview]
Message-ID: <aQxVNPRVdJvbqkiz@black.igk.intel.com> (raw)
In-Reply-To: <aQxQ_orRY1ceokdU@smile.fi.intel.com>
On Thu, Nov 06, 2025 at 09:40:46AM +0200, Andy Shevchenko wrote:
> On Thu, Nov 06, 2025 at 10:58:38AM +0530, Raag Jadav wrote:
> > We have an upcoming driver named "intel_ehl_pse_io". This creates an
> > auxiliary child device for it's GPIO sub-functionality, which matches
> > against "intel_ehl_pse_io.gpio-elkhartlake" and overshoots the current
>
> Looking at the name there is another question: Why do we need 'elkhartlake in
> the GPIO driver's name now? It's a dup to 'ehl' in the first part.
Just kept it for historic consistency and I'm a bit terrible at naming.
Perhaps "gpio-aux"? But that's too generic from subsystem POV.
Open to suggestions.
Raag
> > maximum limit of 32 bytes for auxiliary device id string. Bump the size
> > to 40 bytes to satisfy such cases.
>
> > ---
> > v2: Describe the use case (Greg, Andy)
>
> Thanks for the update!
next prev parent reply other threads:[~2025-11-06 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 5:28 [PATCH v2] mod_devicetable: Bump auxiliary_device_id name size Raag Jadav
2025-11-06 7:40 ` Andy Shevchenko
2025-11-06 7:58 ` Raag Jadav [this message]
2025-11-06 8:05 ` 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=aQxVNPRVdJvbqkiz@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox