Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: zHoktfLbN9oz2PnOOsehz897CaCkM/USJ9lNWT2vBNvVOnUIORxr3oK6At2J+wvRM3/8nSsT/s
 bpK8/g9n7NSA==
IronPort-SDR: 9gg2xpc238vmKvAFtO0z9rs2WaRKb5Ccanxu4lY4sQSQlj1emOL6UxPXR+DQDZxX647RlbqRQo
 NkU61bZW3Vjw==
Date:   Fri, 11 Jun 2021 11:30:59 +0300
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
Message-ID: <YMMfQyZ/SjB6aNOj@lahna>
References: <20210610152823.1653-1-andriy.shevchenko@linux.intel.com>
 <YMMWU1ZMqGoCKOoj@lahna>
 <CAHp75Vf6J8kD9-_ComWeyGks9t507ETPtfQYYLPZikciAir-0w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHp75Vf6J8kD9-_ComWeyGks9t507ETPtfQYYLPZikciAir-0w@mail.gmail.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Precedence: bulk

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.