linux-kernel - Re: [PATCH V2 1/2] dt-bindings: interconnect: Add compatibles for QCS8300 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f649c854-a250-43cf-ae01-82bbb011e7e0@kernel.org>
Date: Fri, 6 Sep 2024 18:49:49 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Raviteja Laggyshetty <quic_rlaggysh@...cinc.com>,
 Georgi Djakov <djakov@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: Konrad Dybcio <konradybcio@...nel.org>, Abel Vesa <abel.vesa@...aro.org>,
 Vladimir Lypak <vladimir.lypak@...il.com>,
 Adam Skladowski <a39.skl@...il.com>, Danila Tikhonov <danila@...xyga.com>,
 Neil Armstrong <neil.armstrong@...aro.org>,
 Andrew Halaney <ahalaney@...hat.com>,
 Odelu Kukatla <quic_okukatla@...cinc.com>,
 Mike Tipton <quic_mdtipton@...cinc.com>, linux-arm-msm@...r.kernel.org,
 linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: interconnect: Add compatibles for
 QCS8300 SoC

On 06/09/2024 17:15, Raviteja Laggyshetty wrote:
> QCS8300 SoC has several bus fabrics that could be controlled
> and tuned dynamically according to the bandwidth demand.

You got quite precise review about subject, which you partially
implemented and then added something more redundant. Look, this is
supposed to be device name. Add QCS8300 RPMh NoC. Drop redundant
information.



> 
> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@...cinc.com>
> ---
>  .../interconnect/qcom,qcs8300-rpmh.yaml       |  72 +++++++
>  .../interconnect/qcom,qcs8300-rpmh.h          | 189 ++++++++++++++++++
>  2 files changed, 261 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,qcs8300-rpmh.yaml
>  create mode 100644 include/dt-bindings/interconnect/qcom,qcs8300-rpmh.h
> 
> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,qcs8300-rpmh.yaml b/Documentation/devicetree/bindings/interconnect/qcom,qcs8300-rpmh.yaml
> new file mode 100644
> index 000000000000..2759b003ebcf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interconnect/qcom,qcs8300-rpmh.yaml
> @@ -0,0 +1,72 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interconnect/qcom,qcs8300-rpmh.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies, Inc. RPMh Network-On-Chip Interconnect on QCS8300

Isn't this just "Qualcomm"? How is in most of other bindings?

I asked not to send us your downstream stuff. I said it about driver,
though... so repeat here: Do not send downstream code, but work on
upstream and use upstream style. This applies to all patches: drivers,
DTS, bindings, everything. So which upstream binding was used as
template for this one here?

Best regards,
Krzysztof