[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAd53p7L6Wcp7wBeHRp7NDPbKJ+kPPAPXi27zWQ08jZbt3M6aA@mail.gmail.com>
Date: Tue, 7 Dec 2021 11:48:23 +0800
From: Kai-Heng Feng <kai.heng.feng@...onical.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
"andy@...nel.org" <andy@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: intel: Assume 0 by default for PNP UID
On Sat, Dec 4, 2021 at 8:49 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
>
> On Saturday, December 4, 2021, Kai-Heng Feng
> <kai.heng.feng@...onical.com> wrote:
> >
> > There's an EHL board that the DSDT doesn't have _UID for pinctrl device,
> > and that causes a NULL pointer dereference in strcmp().
> >
> > So in the absence of _UID, assume it's 0 by default to avoid the issue
> > and get a pinmap.
>
> Do you have updated firmware?
Customer confirmed new code drop from Intel does have _UID defined.
So I guess this patch is not needed anymore?
Kai-Heng
>
>
> --
> With Best Regards,
> Andy Shevchenko
Powered by blists - more mailing lists