From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH v3 1/1] pinctrl: Propagate firmware node from a parent device
Date: Wed, 22 Dec 2021 03:10:54 +0100 [thread overview]
Message-ID: <CACRpkdYe5FHpzvey_hHMLxpYpX0ad9eu0JsaNk_zUkj-1qtQTw@mail.gmail.com> (raw)
In-Reply-To: <20211216151227.58687-1-andriy.shevchenko@linux.intel.com>
On Thu, Dec 16, 2021 at 4:12 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> 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@linux.intel.com>
> ---
> v2: fixed more compilation errors brought by header reshuffling (LKP)
Patch applied! Thanks Andy.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Support Opensource <support.opensource@diasemi.com>,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: Re: [PATCH v3 1/1] pinctrl: Propagate firmware node from a parent device
Date: Wed, 22 Dec 2021 03:10:54 +0100 [thread overview]
Message-ID: <CACRpkdYe5FHpzvey_hHMLxpYpX0ad9eu0JsaNk_zUkj-1qtQTw@mail.gmail.com> (raw)
In-Reply-To: <20211216151227.58687-1-andriy.shevchenko@linux.intel.com>
On Thu, Dec 16, 2021 at 4:12 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> 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@linux.intel.com>
> ---
> v2: fixed more compilation errors brought by header reshuffling (LKP)
Patch applied! Thanks Andy.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-12-22 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:12 [PATCH v3 1/1] pinctrl: Propagate firmware node from a parent device Andy Shevchenko
2021-12-16 15:12 ` Andy Shevchenko
2021-12-16 15:15 ` Adam Thomson
2021-12-16 15:15 ` Adam Thomson
2021-12-17 11:33 ` Charles Keepax
2021-12-17 11:33 ` Charles Keepax
2021-12-22 2:10 ` Linus Walleij [this message]
2021-12-22 2:10 ` Linus Walleij
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=CACRpkdYe5FHpzvey_hHMLxpYpX0ad9eu0JsaNk_zUkj-1qtQTw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=support.opensource@diasemi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.