From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc: Caleb Connolly <caleb.connolly@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Amit Pundir <amit.pundir@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH 6/6] dt-bindings: power: supply: qcom,smb2: add bindings for smb2 driver
Date: Sun, 3 Apr 2022 17:30:07 +0200 [thread overview]
Message-ID: <99f1181b-fde2-43a5-9b6a-c0c3a8b3933f@linaro.org> (raw)
In-Reply-To: <20220403133122.GA49428@9a2d8922b8f1>
On 03/04/2022 15:31, Kuldeep Singh wrote:
> On Sun, Apr 03, 2022 at 09:56:25AM +0200, Krzysztof Kozlowski wrote:
>> On 03/04/2022 09:14, Kuldeep Singh wrote:
>>> On Fri, Apr 01, 2022 at 09:26:43PM +0100, Caleb Connolly wrote:
>>>> Add devicetree bindings for the Qualcomm PMI8998/PM660 SMB2 charger
>>>> drivers.
>>>>
>>
>> (...)
>>
>>>
>>>> + pmic {
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>> + #interrupt-cells = <4>;
>>>> +
>>>> + smb2@1000 {
>>>> + compatible = "qcom,pmi8998-smb2";
>>>> + reg = <0x1000>;
>>>> +
>>>> + interrupts = <0x2 0x13 0x4 IRQ_TYPE_EDGE_BOTH>;
>>>> + interrupt-names = "usb-plugin";
>>>> +
>>>
>>> In-between new lines may not be required.
>>> And DTs use tabs instead of 2 spaces, we can follow that here also.
>>
>> The DT examples in bindings use spaces. Either two (like YAML) or four
>> (for easier reading).
>
> ok, since example snippet is taken from DT that's why I said four
> spaces(tab) as it will be closest to actual env.
You said "use tabs", which is 8 spaces in Linux. So to clarify - we do
not use tabs here, so do not use tabs.
>>>> + io-channels = <&pmi8998_rradc 3>,
>>>> + <&pmi8998_rradc 4>;
>>>> + io-channel-names = "usbin_i",
>>>> + "usbin_v";
>>>
>>> Channel-names can be written in one line.
>>
>> They match the format of io-channels, so this is quite readable.
>
> io-channels doesn't exceed max characters in line(i.e 75) even after
> being clubbed. Won't be better if kept in one line?
> This might be personal perspective but I thought it's worth mentioning.
I find current code readable. The other option would be fine as well,
kind of does not matter to me much.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-04-03 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 20:26 [PATCH 0/6] power: supply: introduce the Qualcomm smb2 Caleb Connolly
2022-04-01 20:26 ` [PATCH 1/6] power: supply: add Qualcomm SMB2 driver Caleb Connolly
2022-04-01 22:53 ` Sebastian Reichel
2022-04-02 15:45 ` Caleb Connolly
2022-04-04 13:11 ` Bjorn Andersson
2022-04-01 20:26 ` [PATCH 2/6] arm64: dts: qcom: pmi8998: add smb2 node Caleb Connolly
2022-04-02 14:40 ` Krzysztof Kozlowski
2022-04-01 20:26 ` [PATCH 3/6] arm64: dts: sdm845-oneplus: enable smb2 Caleb Connolly
2022-04-01 20:26 ` [PATCH 4/6] arm64: dts: qcom: sdm845-db845c: " Caleb Connolly
2022-04-01 20:26 ` [PATCH 5/6] arm64: dts: qcom: sdm845-xiaomi-beryllium " Caleb Connolly
2022-04-01 20:26 ` [PATCH 6/6] dt-bindings: power: supply: qcom,smb2: add bindings for smb2 driver Caleb Connolly
2022-04-01 23:03 ` Sebastian Reichel
2022-04-02 15:44 ` Caleb Connolly
2022-04-02 14:22 ` Krzysztof Kozlowski
2022-04-02 15:50 ` Caleb Connolly
2022-04-03 7:14 ` Kuldeep Singh
2022-04-03 7:56 ` Krzysztof Kozlowski
2022-04-03 13:31 ` Kuldeep Singh
2022-04-03 15:30 ` Krzysztof Kozlowski [this message]
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=99f1181b-fde2-43a5-9b6a-c0c3a8b3933f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=singh.kuldeep87k@gmail.com \
--cc=sre@kernel.org \
--cc=sumit.semwal@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).