From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: serial: Describe ARM dcc interface
Date: Tue, 2 Jan 2024 16:32:31 +0100 [thread overview]
Message-ID: <08546f36-9f88-4fd9-ba4e-5d6ee21cd60f@amd.com> (raw)
In-Reply-To: <de6370c5-5cd1-409a-8716-99dd7738d30d@linaro.org>
On 12/22/23 09:20, Krzysztof Kozlowski wrote:
> On 21/12/2023 15:05, Michal Simek wrote:
>> Debug Communication Channel (DCC) provides the way how to pass data between
>> target CPU and host via JTAG interface. Every CPU has own interface for
>> communication via dbgdtrtx_el0 and dbgdtrrx_el0 registers.
>>
>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>> ---
>>
>> This communication interface is used for flash programming on Xilinx
>> SOCs from U-Boot.
>> https://source.denx.de/u-boot/u-boot/-/blob/master/drivers/serial/arm_dcc.c
>>
>> ---
>> .../devicetree/bindings/serial/arm,dcc.yaml | 30 +++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/serial/arm,dcc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/serial/arm,dcc.yaml b/Documentation/devicetree/bindings/serial/arm,dcc.yaml
>> new file mode 100644
>> index 000000000000..fd0589356617
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/serial/arm,dcc.yaml
>> @@ -0,0 +1,30 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/serial/arm,dcc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: ARM DCC (Data communication channel) serial emulation
>> +
>> +maintainers:
>> + - Michal Simek <michal.simek@amd.com>
>> +
>> +description: |
>> + ARM DCC (Data communication channel) serial emulation interface available
>> + via JTAG can be also used as one of serial line tightly coupled with every
>> + ARM CPU available in the system.
>> +
>> +properties:
>> + compatible:
>> + const: arm,dcc
>> +
>> +required:
>> + - compatible
>
> no allOf: with $ref to serial.yaml? Does it differ somehow?
Valid one could be only nodename format and maybe label.
Others are not relevant. But if that's fine I can also add it.
Thanks,
Michal
next prev parent reply other threads:[~2024-01-02 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 14:05 [PATCH] dt-bindings: serial: Describe ARM dcc interface Michal Simek
2023-12-21 21:11 ` Rob Herring
2023-12-22 8:20 ` Krzysztof Kozlowski
2024-01-02 15:32 ` Michal Simek [this message]
2024-01-03 20:22 ` Rob Herring
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=08546f36-9f88-4fd9-ba4e-5d6ee21cd60f@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@kernel.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