From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Canfeng Zhuang <quic_czhuang@quicinc.com>,
Derek Kiernan <derek.kiernan@amd.com>,
Dragan Cvetic <dragan.cvetic@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: misc: merge qcom,qrc
Date: Sun, 3 Mar 2024 20:07:05 +0100 [thread overview]
Message-ID: <e13610f6-6e09-4073-bc26-108b76c2a88f@linaro.org> (raw)
In-Reply-To: <20240304-qcom_qrc-v1-2-2a709f95fd61@quicinc.com>
On 03/03/2024 17:53, Canfeng Zhuang wrote:
> Merge Qualcomm-specific qrc binding
Merge? No, instead describe the hardware.
Similar problem with the sibject.
>
> Signed-off-by: Canfeng Zhuang <quic_czhuang@quicinc.com>
> ---
> .../devicetree/bindings/misc/qcom,qrc.yaml | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/misc/qcom,qrc.yaml b/Documentation/devicetree/bindings/misc/qcom,qrc.yaml
> new file mode 100644
> index 000000000000..730efd679ba0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/qcom,qrc.yaml
> @@ -0,0 +1,32 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/misc/qcom,qrc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Robotics Communication Driver
Driver? Unfortunately bindings are for hardware, not drivers.
> +
> +maintainers:
> + - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + The QRC (Qualcomm Robotics Communication) driver is used for information interaction
Agaim, driver?
> + between the robot control board and the main board when using a uart port connection.
> + This Driver will support uart read & write and robot control board
No, describe the hardware.
> + reset function.
> +
> +properties:
> + compatible:
> + const: qcom,qrc-uart
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + qrc: qcom,qrc_uart {
How does it remotely look like upstream DTS? Please don't send
downstream/vendor DTS before cleaning it up. Before posting, please read
submitting patches and/or quite extensive Qualcomm upstreaming guides.
> + compatible = "qcom,qrc-uart";
Nope, so this is just to instantiate Linux device? No resources? This
looks really incomplete.
> + };
> +
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-03 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 16:53 [PATCH 0/2] QCOM QRC device driver Canfeng Zhuang
2024-03-03 16:53 ` [PATCH 1/2] misc: qualcomm: QRC driver for Robotic SDK MCU Canfeng Zhuang
2024-03-03 17:17 ` Greg Kroah-Hartman
2024-03-03 19:11 ` Krzysztof Kozlowski
2024-03-03 22:55 ` kernel test robot
2024-03-03 23:29 ` kernel test robot
2024-03-04 0:41 ` kernel test robot
2024-03-03 16:53 ` [PATCH 2/2] dt-bindings: misc: merge qcom,qrc Canfeng Zhuang
2024-03-03 19:07 ` Krzysztof Kozlowski [this message]
2024-03-04 19:35 ` [PATCH 0/2] QCOM QRC device driver Bjorn Andersson
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=e13610f6-6e09-4073-bc26-108b76c2a88f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=derek.kiernan@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_czhuang@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@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).