From: Linus Walleij <linus.walleij@linaro.org>
To: Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
marcel.ziswiler@toradex.com,
Oleksandr Suvorov <oleksandr.suvorov@toradex.com>,
Oleksandr Suvorov <oleksandr.suvorov@foundries.io>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: stmpe: Support disabling sub-functions
Date: Thu, 28 Oct 2021 02:37:43 +0200 [thread overview]
Message-ID: <CACRpkdY95RSDbNm5rMtSZmbDW9=+KtY7dAfA8PGarmQ-CF6dnQ@mail.gmail.com> (raw)
In-Reply-To: <20211027082155.206449-1-francesco.dolcini@toradex.com>
On Wed, Oct 27, 2021 at 10:23 AM Francesco Dolcini
<francesco.dolcini@toradex.com> wrote:
> From: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
>
> Add support of sub-functions disabling. It allows one to define
> an stmpe sub-function device in devicetree, but keep it disabled.
>
> Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
> Cc: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Looks helpful.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-28 0:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:21 [PATCH] mfd: stmpe: Support disabling sub-functions Francesco Dolcini
2021-10-27 16:14 ` Marcel Ziswiler
2021-10-28 0:37 ` Linus Walleij [this message]
2021-11-01 9:48 ` Francesco Dolcini
2021-11-01 12:13 ` Lee Jones
2021-11-02 8:21 ` Francesco Dolcini
2021-11-02 10:48 ` Lee Jones
2021-11-24 15:45 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2020-12-26 9:47 Oleksandr Suvorov
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='CACRpkdY95RSDbNm5rMtSZmbDW9=+KtY7dAfA8PGarmQ-CF6dnQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=francesco.dolcini@toradex.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=oleksandr.suvorov@foundries.io \
--cc=oleksandr.suvorov@toradex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).