From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v1 1/1] pinctrl: intel: Check against matching data instead of ACPI companion
Date: Fri, 11 Jun 2021 11:30:59 +0300 [thread overview]
Message-ID: <YMMfQyZ/SjB6aNOj@lahna> (raw)
In-Reply-To: <CAHp75Vf6J8kD9-_ComWeyGks9t507ETPtfQYYLPZikciAir-0w@mail.gmail.com>
On Fri, Jun 11, 2021 at 11:16:23AM +0300, Andy Shevchenko wrote:
> On Fri, Jun 11, 2021 at 10:53 AM Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> >
> > On Thu, Jun 10, 2021 at 06:28:23PM +0300, Andy Shevchenko wrote:
> > > In some cases we may get a platform device that has ACPI companion
> > > which is different to the pin control described in the ACPI tables.
> > > This is primarily happens when device is instantiated by board file.
> >
> > Can you point which board file in the mainline kernel has this issue? If
> > not then I don't think it makes sense to add code like this.
>
> To my knowledge we don't have such enumeration in the upstream (but it
> may be done by third parties against any of our controllers enumerated
> by UID, like Broxton or Gemini Lake).
So let's add it when we have such thing in the mainline.
For the rest Intel drivers we always supply the SoC information so this
is not a problem.
prev parent reply other threads:[~2021-06-11 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 15:28 [PATCH v1 1/1] pinctrl: intel: Check against matching data instead of ACPI companion Andy Shevchenko
2021-06-11 7:52 ` Mika Westerberg
2021-06-11 8:16 ` Andy Shevchenko
2021-06-11 8:30 ` Mika Westerberg [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=YMMfQyZ/SjB6aNOj@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=henning.schild@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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