From: Rob Herring <robh@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: media: max9286: Describe gpio-hog
Date: Fri, 5 Mar 2021 15:51:09 -0600 [thread overview]
Message-ID: <20210305215109.GA703883@robh.at.kernel.org> (raw)
In-Reply-To: <20210215172447.2026514-2-jacopo+renesas@jmondi.org>
On Mon, Feb 15, 2021 at 06:24:44PM +0100, Jacopo Mondi wrote:
> The MAX9286 GMSL deserializer features gpio controller capabilities,
> as it provides 2 GPIO lines.
>
> As establishing a regulator that uses one of the GPIO lines and
> enabling/disabling it at run-time in the max9286 won't work due to
> a circular dependency on the gpio-controller/regulator creation, allow
> the usage of a gpio-hog for that purpose.
>
> The usage of the gpio-hog is required in designs where the MAX9286
> GPIO lines control the remote cameras power.
>
> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> ---
> .../devicetree/bindings/media/i2c/maxim,max9286.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> index ee16102fdfe7..9d5ecfd2397c 100644
> --- a/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml
> @@ -50,6 +50,15 @@ properties:
> '#gpio-cells':
> const: 2
>
> + camvdd_en:
I don't think we want to document all the GPIO hogs, but rather have a
pattern we can check. IOW, having node name pattern we match on. I think
the core schemas has this now.
> + type: object
> + properties:
> + gpio-hog: true
> + gpios: true
> + output-low: true
> + line-name:
> + const: "CAMVDD_EN"
> +
> maxim,reverse-channel-microvolt:
> minimum: 30000
> maximum: 200000
> --
> 2.30.0
>
next prev parent reply other threads:[~2021-03-05 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:24 [PATCH 0/4] arm64: dts: renesas: Enable GMSL on R8A77970 V3M Eagle Jacopo Mondi
2021-02-15 17:24 ` [PATCH 1/4] dt-bindings: media: max9286: Describe gpio-hog Jacopo Mondi
2021-03-05 21:51 ` Rob Herring [this message]
2021-02-15 17:24 ` [PATCH 2/4] arm64: dts: renesas: eagle: Enable MAX9286 Jacopo Mondi
2021-02-15 17:24 ` [PATCH 3/4] arm64: dts: renesas: eagle: Add GMSL .dtsi Jacopo Mondi
2021-02-15 17:24 ` [PATCH 4/4] arm64: dts: renesas: eagle: Include eagle-gmsl Jacopo Mondi
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=20210305215109.GA703883@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).