From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Documentation: dt-bindings: media: i2c: Add ROHM BU64754 bindings
Date: Sun, 17 Sep 2023 11:37:07 +0200 [thread overview]
Message-ID: <22bc83c7-17c3-f8a0-b1de-5d6b2e1e29b2@linaro.org> (raw)
In-Reply-To: <20230915165946.4183839-2-kieran.bingham@ideasonboard.com>
On 15/09/2023 18:59, Kieran Bingham wrote:
> Add YAML device tree bindings for the ROHM BU64754 VCM Motor Driver for
> Camera Autofocus.
>
> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> ---
...
> +properties:
> + compatible:
> + items:
> + - enum:
> + - rohm,bu64754
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply:
If the supply is not required, how the driver gets any power?
> + description:
> + Definition of the regulator used as VDD power supply to the driver.
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + lens@76 {
> + compatible = "rohm,bu64754";
> + reg = <0x76>;
> + vdd-supply = <&cam1_reg>;
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 90f13281d297..f43e0ffcaf56 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18570,6 +18570,13 @@ S: Supported
> F: drivers/iio/light/rohm-bu27008.c
> F: drivers/iio/light/rohm-bu27034.c
>
> +ROHM BU64754 MOTOR DRIVER FOR CAMERA AUTOFOCUS
> +M: Kieran Bingham <kieran.bingham@ideasonboard.com>
> +L: linux-media@vger.kernel.org
> +S: Maintained
> +T: git git://linuxtv.org/media_tree.git
Do you have push rights there? The git entry is for entries where you
maintain, which means: you accept and apply patches. This does not look
like the case, so copying subsystem Git entry is pointless. Subsystem
maintainer defines the git tree, not you.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-17 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230915165946.4183839-1-kieran.bingham@ideasonboard.com>
2023-09-15 16:59 ` [PATCH 1/2] Documentation: dt-bindings: media: i2c: Add ROHM BU64754 bindings Kieran Bingham
2023-09-15 21:13 ` Conor Dooley
2023-09-17 10:26 ` Kieran Bingham
2023-09-17 9:37 ` Krzysztof Kozlowski [this message]
2023-09-17 10:33 ` Kieran Bingham
2023-09-17 17:27 ` Krzysztof Kozlowski
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=22bc83c7-17c3-f8a0-b1de-5d6b2e1e29b2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.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).