From: Rob Herring <robh@kernel.org>
To: Axe Yang <axe.yang@mediatek.com>
Cc: Tian Tao <tiantao6@hisilicon.com>,
Satya Tangirala <satyat@google.com>,
linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mediatek@lists.infradead.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
angelogioacchino.delregno@collabora.com,
Chaotian Jing <chaotian.jing@mediatek.com>,
devicetree@vger.kernel.org, Yue Hu <huyue2@yulong.com>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kiwoong Kim <kwmad.kim@samsung.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Eric Biggers <ebiggers@google.com>,
Andrew Jeffery <andrew@aj.id.au>,
Stephen Boyd <swboyd@chromium.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Lucas Stach <dev@lynxeye.de>
Subject: Re: [PATCH v9 1/3] dt-bindings: mmc: mtk-sd: extend interrupts and pinctrls properties
Date: Tue, 29 Mar 2022 18:00:46 -0500 [thread overview]
Message-ID: <YkOPnkFz2DDx7Qr0@robh.at.kernel.org> (raw)
In-Reply-To: <20220329032913.8750-2-axe.yang@mediatek.com>
On Tue, 29 Mar 2022 11:29:11 +0800, Axe Yang wrote:
> Extend interrupts and pinctrls for SDIO wakeup interrupt feature.
> This feature allow SDIO devices alarm asynchronous interrupt to host
> even when host stop providing clock to SDIO card. An extra wakeup
> interrupt and pinctrl states for SDIO DAT1 pin state switching are
> required in this scenario.
>
> Signed-off-by: Axe Yang <axe.yang@mediatek.com>
> ---
> .../devicetree/bindings/mmc/mtk-sd.yaml | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-03-29 23:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 3:29 [PATCH v9 0/3] mmc: mediatek: add support for SDIO async IRQ Axe Yang
2022-03-29 3:29 ` [PATCH v9 1/3] dt-bindings: mmc: mtk-sd: extend interrupts and pinctrls properties Axe Yang
2022-03-29 23:00 ` Rob Herring [this message]
2022-04-01 9:22 ` Ulf Hansson
2022-04-01 9:34 ` Ulf Hansson
2022-04-01 17:43 ` Rob Herring
2022-04-06 9:38 ` Axe Yang
2022-03-29 3:29 ` [PATCH v9 2/3] mmc: core: Add support for SDIO wakeup interrupt Axe Yang
2022-03-29 10:33 ` AngeloGioacchino Del Regno
2022-03-30 8:03 ` Axe Yang
2022-04-01 12:42 ` Ulf Hansson
2022-04-06 9:41 ` Axe Yang
2022-03-29 3:29 ` [PATCH v9 3/3] mmc: mediatek: add support for SDIO eint wakup IRQ Axe Yang
2022-03-30 8:30 ` Chaotian Jing
2022-04-04 15:01 ` Ulf Hansson
2022-05-19 11:53 ` Axe Yang
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=YkOPnkFz2DDx7Qr0@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andrew@aj.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axe.yang@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=dev@lynxeye.de \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@google.com \
--cc=huyue2@yulong.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=satyat@google.com \
--cc=swboyd@chromium.org \
--cc=tiantao6@hisilicon.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).