From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
David Heidelberg <david.heidelberg@collabora.com>
Cc: krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, y.oudjana@protonmail.com,
jason-jh.lin@mediatek.com, ck.hu@mediatek.com,
fparent@baylibre.com, rex-bc.chen@mediatek.com,
tinghan.shen@mediatek.com, chun-jie.chen@mediatek.com,
weiyi.lu@mediatek.com, ikjn@chromium.org,
miles.chen@mediatek.com, sam.shih@mediatek.com,
wenst@chromium.org, bgolaszewski@baylibre.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org,
konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
martin.botka@somainline.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, paul.bouchara@somainline.org,
kernel@collabora.com
Subject: Re: [PATCH v3 4/7] dt-bindings: clock: mediatek: Add clock driver bindings for MT6795
Date: Mon, 27 Jun 2022 09:44:50 +0200 [thread overview]
Message-ID: <2111b4a7-d195-0333-1d43-02fcd91f89e2@collabora.com> (raw)
In-Reply-To: <ee945844-5d78-7c2b-215e-25fe5617b481@linaro.org>
Il 26/06/22 12:31, Krzysztof Kozlowski ha scritto:
> On 26/06/2022 11:47, David Heidelberg wrote:
>> On 25/06/2022 22:29, Krzysztof Kozlowski wrote:
>>> On 24/06/2022 11:35, AngeloGioacchino Del Regno wrote:
>>>> Add the bindings for the clock drivers of the MediaTek Helio X10
>>>> MT6795 SoC.
>>>>
>>>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>>> ---
>>>> .../bindings/clock/mediatek,mt6795-clock.yaml | 66 +++++++++++++++++
>>>> .../clock/mediatek,mt6795-sys-clock.yaml | 74 +++++++++++++++++++
>>>> 2 files changed, 140 insertions(+)
>>>> create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml
>>>> create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml b/Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml
>>>> new file mode 100644
>>>> index 000000000000..795fb18721c3
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml
>>>> @@ -0,0 +1,66 @@
>>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>>>> +%YAML 1.2
>>>> +---
>>>> +$id: "http://devicetree.org/schemas/clock/mediatek,mt6795-clock.yaml#"
>>>> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
>>>> +
>>>> +title: MediaTek Functional Clock Controller for MT6795
>>>> +
>>>> +maintainers:
>>>> + - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>>> + - Chun-Jie Chen <chun-jie.chen@mediatek.com>
>>>> +
>>>> +description: |
>>>> + The clock architecture in MediaTek like below
>>>> + PLLs -->
>>>> + dividers -->
>>>> + muxes
>>>> + -->
>>>> + clock gate
>>>> +
>>>> + The devices provide clock gate control in different IP blocks.
>>>> +
>>>> +properties:
>>>> + compatible:
>>>> + enum:
>>>> + - mediatek,mt6795-mfgcfg
>>>> + - mediatek,mt6795-vdecsys
>>>> + - mediatek,mt6795-vencsys
>>>> +
>>>> + reg:
>>>> + maxItems: 1
>>>> +
>>>> + '#clock-cells':
>>>> + const: 1
>>>> +
>>>> +required:
>>>> + - compatible
>>>> + - reg
>>>> + - '#clock-cells'
>>>> +
>>>> +additionalProperties: false
>>>> +
>>>> +examples:
>>>> + - |
>>>> + soc {
>>>> + #address-cells = <2>;
>>>> + #size-cells = <2>;
>>>> +
>>>> + mfgcfg: clock-controller@13000000 {
>>>> + compatible = "mediatek,mt6795-mfgcfg";
>>>> + reg = <0 0x13000000 0 0x1000>;
>>>> + #clock-cells = <1>;
>>>> + };
>>>> +
>>>> + vdecsys: clock-controller@16000000 {
>>>> + compatible = "mediatek,mt6795-vdecsys";
>>>> + reg = <0 0x16000000 0 0x1000>;
>>>> + #clock-cells = <1>;
>>>> + };
>>>> +
>>>> + vencsys: clock-controller@18000000 {
>>>> + compatible = "mediatek,mt6795-vencsys";
>>>> + reg = <0 0x18000000 0 0x1000>;
>>>> + #clock-cells = <1>;
>>>> + };
>>>> + };
>>>> diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml b/Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml
>>>> new file mode 100644
>>>> index 000000000000..44b96af9ceaf
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml
>>>> @@ -0,0 +1,74 @@
>>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>>>> +%YAML 1.2
>>>> +---
>>>> +$id: "http://devicetree.org/schemas/clock/mediatek,mt6795-sys-clock.yaml#"
>>>> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
>>>> +
>>>> +title: MediaTek System Clock Controller for MT6795
>>>> +
>>>> +maintainers:
>>>> + - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>>> + - Chun-Jie Chen <chun-jie.chen@mediatek.com>
>>>> +
>>>> +description:
>>>> + The Mediatek system clock controller provides various clocks and system configuration
>>> Wrap according to Linux coding convention, so at 80.
>>
>> What I understood that 100 length was agreed [1] as a limit. I haven't
>> noticed any recent change regarding to line length.
>>
>> [1]
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bdc48fa11e46f867ea4d75fa59ee87a7f48be144
>
> The coding style (also in change above) clearly states:
> "The preferred limit on the length of a single line is 80 columns."
> Just read the first line of new diff/hunk...
>
> checkpatch was indeed long time converted not to complain on 80 but on
> 100, but that does not change coding style. The point of that was only
> to accept 100 wrapping when it is beneficial, iow, it increases the
> code readability.
>
> It's not the case here and coding style clearly asks for 80. Wrap at 80.
>
Hello David, Krzysztof,
there's no problem at all, I can resend... after all, it's a fast fix and
all it takes is 10 minutes of my time!
Cheers,
Angelo
next prev parent reply other threads:[~2022-06-27 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:35 [PATCH v3 0/7] MediaTek Helio X10 MT6795 - Clock drivers AngeloGioacchino Del Regno
2022-06-24 9:35 ` [PATCH v3 1/7] dt-bindings: mediatek: Document MT6795 system controllers bindings AngeloGioacchino Del Regno
2022-06-24 9:35 ` [PATCH v3 2/7] dt-bindings: clock: Add MediaTek Helio X10 MT6795 clock bindings AngeloGioacchino Del Regno
2022-06-25 20:30 ` Krzysztof Kozlowski
2022-06-27 8:49 ` AngeloGioacchino Del Regno
2022-06-27 8:59 ` Krzysztof Kozlowski
2022-06-24 9:35 ` [PATCH v3 3/7] dt-bindings: reset: Add bindings for MT6795 Helio X10 reset controllers AngeloGioacchino Del Regno
2022-06-25 20:30 ` Krzysztof Kozlowski
2022-06-24 9:35 ` [PATCH v3 4/7] dt-bindings: clock: mediatek: Add clock driver bindings for MT6795 AngeloGioacchino Del Regno
2022-06-24 17:26 ` Rob Herring
2022-06-25 20:29 ` Krzysztof Kozlowski
2022-06-26 9:47 ` David Heidelberg
2022-06-26 10:31 ` Krzysztof Kozlowski
2022-06-27 7:44 ` AngeloGioacchino Del Regno [this message]
2022-06-24 9:35 ` [PATCH v3 5/7] clk: mediatek: clk-apmixed: Remove unneeded __init annotation AngeloGioacchino Del Regno
2022-06-25 0:07 ` Miles Chen
2022-06-24 9:35 ` [PATCH v3 6/7] clk: mediatek: Export required symbols to compile clk drivers as module AngeloGioacchino Del Regno
2022-06-24 9:35 ` [PATCH v3 7/7] clk: mediatek: Add MediaTek Helio X10 MT6795 clock drivers AngeloGioacchino Del Regno
2022-06-25 0:07 ` Miles Chen
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=2111b4a7-d195-0333-1d43-02fcd91f89e2@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=bgolaszewski@baylibre.com \
--cc=chun-jie.chen@mediatek.com \
--cc=ck.hu@mediatek.com \
--cc=david.heidelberg@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=ikjn@chromium.org \
--cc=jason-jh.lin@mediatek.com \
--cc=kernel@collabora.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=paul.bouchara@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=rex-bc.chen@mediatek.com \
--cc=sam.shih@mediatek.com \
--cc=sboyd@kernel.org \
--cc=tinghan.shen@mediatek.com \
--cc=weiyi.lu@mediatek.com \
--cc=wenst@chromium.org \
--cc=y.oudjana@protonmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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