From: Rob Herring <robh@kernel.org>
To: Catalin Popescu <catalin.popescu@leica-geosystems.com>
Cc: ulf.hansson@linaro.org, krzk+dt@kernel.org, conor+dt@kernel.org,
p.zabel@pengutronix.de, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
m.felsch@pengutronix.de,
bsp-development.geo@leica-geosystems.com
Subject: Re: [PATCH 1/2] dt-bindings: mmc: mmc-pwrseq-simple: add support for reset control
Date: Sat, 5 Oct 2024 13:26:32 -0500 [thread overview]
Message-ID: <20241005182632.GA496820-robh@kernel.org> (raw)
In-Reply-To: <20241004120740.2887776-1-catalin.popescu@leica-geosystems.com>
On Fri, Oct 04, 2024 at 02:07:39PM +0200, Catalin Popescu wrote:
> Add compatible value "mmc-pwrseq-simple-reset" to support reset control
> instead of gpios. Reset controls being refcounted, they allow to use
> shared resets or gpios across drivers. Support of reset control is
> limited to one single reset control.
Can't you do this without a binding change? Just use reset controls when
there is only 1 GPIO.
>
> Signed-off-by: Catalin Popescu <catalin.popescu@leica-geosystems.com>
> ---
> .../bindings/mmc/mmc-pwrseq-simple.yaml | 21 +++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2024-10-05 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 12:07 [PATCH 1/2] dt-bindings: mmc: mmc-pwrseq-simple: add support for reset control Catalin Popescu
2024-10-04 12:07 ` [PATCH 2/2] mmc: pwrseq_simple: " Catalin Popescu
2024-10-05 14:19 ` kernel test robot
2024-10-05 18:26 ` Rob Herring [this message]
2024-10-07 15:32 ` [PATCH 1/2] dt-bindings: mmc: mmc-pwrseq-simple: " POPESCU Catalin
2024-10-07 15:59 ` Rob Herring
2024-10-08 7:15 ` POPESCU Catalin
2024-10-21 6:52 ` Marco Felsch
2024-10-06 12:37 ` Krzysztof Kozlowski
2024-10-07 15:17 ` POPESCU Catalin
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=20241005182632.GA496820-robh@kernel.org \
--to=robh@kernel.org \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=catalin.popescu@leica-geosystems.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=ulf.hansson@linaro.org \
/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).