From: Krzysztof Kozlowski <krzk@kernel.org>
To: wangshuaijie@awinic.com, dmitry.torokhov@gmail.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jeff@labundy.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: liweilei@awinic.com, kangjiajun@awinic.com
Subject: Re: [PATCH V2 1/5] dt-bindings: input: Add YAML to Awinic sar sensor.
Date: Wed, 5 Jun 2024 12:20:31 +0200 [thread overview]
Message-ID: <1c61d5b5-d9c0-4fa3-8267-8aaf6c441b75@kernel.org> (raw)
In-Reply-To: <20240605091143.163789-2-wangshuaijie@awinic.com>
On 05/06/2024 11:11, wangshuaijie@awinic.com wrote:
> From: shuaijie wang <wangshuaijie@awinic.com>
>
> Add the awinic,aw_sar.yaml file to adapt to the awinic sar sensor driver.
Subject: drop final stops. From all your patches.
>
> Signed-off-by: shuaijie wang <wangshuaijie@awinic.com>
> ---
No changelog, so nothing improved?
> .../bindings/input/awinic,aw_sar.yaml | 125 ++++++++++++++++++
No underscores, but rather awinic,aw96103.yaml
> 1 file changed, 125 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/awinic,aw_sar.yaml
>
> diff --git a/Documentation/devicetree/bindings/input/awinic,aw_sar.yaml b/Documentation/devicetree/bindings/input/awinic,aw_sar.yaml
> new file mode 100644
> index 000000000000..2560ef09d3d0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/awinic,aw_sar.yaml
> @@ -0,0 +1,125 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/input/awinic,aw_sar.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Awinic sar sensor driver family
driver as Linux driver or some other hardware meaning? If first, then
drop and describe hardware.
> +
> +maintainers:
> + - Shuaijie Wang <wangshuaijie@awinic.com>
Missing description. You already got question about meaning of sar and
indeed nothing improved.
> +
> +properties:
> + compatible:
> + enum:
> + - awinic,aw96103
> + - awinic,aw96105
> + - awinic,aw96303
> + - awinic,aw96305
> + - awinic,aw96308
> +
> + reg:
> + maxItems: 1
> +
> + irq-gpio:
> + maxItems: 1
> +
> + awinic,sar-label:
label is a string, not number.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Set the label of the SAR(Specific Absorption Rate) sensor.
> + It is set to 0 if one awinic sar chip is used.
> + If two awinic sar chips are used, awinic,sar-label in the first
> + awinic-sar should be set to 0 and awinic,sar-label in the second
> + awinic-sar should be set to 1.
Sorry, no instance indexing. Drop.
> +
> +
No need for two line breaks.
> + awinic,regulator-power-supply:
> + description:
> + Choose if you want to use a regulator to power the chip. Then the
> + vccX-supply has to be set.
> +
> + vcc0-supply:
> + description:
> + Optional regulator for chip, 1.7V-3.6V.
> + If two awinic sar chips are used, the first regulator
> + should set the ID to vcc0-supply and the second regulator
> + should set the ID to vcc1-supply.
> +
> + awinic,channel-use-mask:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + The mask of channels used.
> + Configure according to the specific chip channel used.
> + Bit[31:0] Each bit represents a channel.
> + If the customer uses ch0 and ch2, then channel_use_mask=<0x05>
> + For a 3-channel chip, the maximum value is 0x07;
> + For a 5-channel chip, the maximum value is 0x1F;
> + For a 8-channel chip, the maximum value is 0xFF;
> +
> + awinic,update-fw:
> + type: boolean
> + description:
> + Choose if you want to update the firmware.
Not much improve in explanation or rationale. Why do you want to update
FW every time? Explain this in property description.
I mostly skipped the rest, because it does not look like you addresses
previous feedback.
...
> +
> +required:
> + - compatible
> + - reg
> + - irq-gpio
> + - awinic,sar-label
> + - awinic,channel-use-mask
> +
> +unevaluatedProperties: false
Missing some ref, like dai-common or component... or this is supposed to
be additionalProperties: false instead.
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + awinic-sar@12 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
I still have no clue what is sar and there is no description in this
binding.
> + compatible = "awinic,aw96308";
> + reg = <0x12>;
> + irq-gpio = <&tlmm 72 0>;
Use proper defines.
> + awinic,sar-label = < 0 >;
Do not introduce different coding style. Drop spaces. See DTS coding style.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-05 10:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 9:11 [PATCH V2 0/5] Add support for Awinic SAR sensor wangshuaijie
2024-06-05 9:11 ` [PATCH V2 1/5] dt-bindings: input: Add YAML to Awinic sar sensor wangshuaijie
2024-06-05 10:20 ` Krzysztof Kozlowski [this message]
2024-07-12 9:47 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 2/5] Add universal interface for the aw_sar driver wangshuaijie
2024-06-05 9:11 ` [PATCH V2 3/5] Add aw9610x series related interfaces to " wangshuaijie
2024-06-05 10:22 ` Krzysztof Kozlowski
2024-07-12 9:50 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 4/5] Add aw963xx " wangshuaijie
2024-06-05 10:29 ` Krzysztof Kozlowski
2024-07-12 9:48 ` wangshuaijie
2024-06-05 9:11 ` [PATCH V2 5/5] Add support for Awinic sar sensor wangshuaijie
2024-06-05 10:33 ` Krzysztof Kozlowski
2024-07-12 9:48 ` wangshuaijie
2024-06-05 12:09 ` kernel test robot
2024-06-06 18:32 ` kernel test robot
2024-06-08 2:22 ` kernel test robot
2024-06-06 3:04 ` [PATCH V2 0/5] Add support for Awinic SAR sensor Jeff LaBundy
2024-07-12 9:49 ` wangshuaijie
2024-07-12 12:02 ` Krzysztof Kozlowski
2024-07-25 12:48 ` wangshuaijie
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=1c61d5b5-d9c0-4fa3-8267-8aaf6c441b75@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=kangjiajun@awinic.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liweilei@awinic.com \
--cc=robh@kernel.org \
--cc=wangshuaijie@awinic.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).