[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB9PR10MB465262B9D0D856CDE85454CC80779@DB9PR10MB4652.EURPRD10.PROD.OUTLOOK.COM>
Date: Thu, 16 Dec 2021 15:15:23 +0000
From: Adam Thomson <Adam.Thomson.Opensource@...semi.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"patches@...nsource.cirrus.com" <patches@...nsource.cirrus.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: Charles Keepax <ckeepax@...nsource.cirrus.com>,
Richard Fitzgerald <rf@...nsource.cirrus.com>,
Linus Walleij <linus.walleij@...aro.org>,
Support Opensource <Support.Opensource@...semi.com>
Subject: RE: [PATCH v3 1/1] pinctrl: Propagate firmware node from a parent
device
On 16 December 2021 15:12, Andy Shevchenko wrote:
> When creating MFD platform devices the firmware node is left unset.
> This, in particular, prevents GPIO library to use it for different
> purposes. Propagate firmware node from the parent device and let
> GPIO library do the right thing.
>
> While at it, slightly modify the headers to reflect the usage of APIs.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
For DA9062 updates:
Reviewed-by: Adam Thomson <Adam.Thomson.Opensource@...semi.com>
Powered by blists - more mailing lists