Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: linux-kernel@vger.kernel.org, michal.simek@xilinx.com,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, monstr@monstr.eu,
	Rob Herring <robh+dt@kernel.org>,
	git@xilinx.com, devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH] dt-bindings: serial: Describe ARM dcc interface
Date: Thu, 21 Dec 2023 15:11:56 -0600	[thread overview]
Message-ID: <170319311633.101509.1532196763061569676.robh@kernel.org> (raw)
In-Reply-To: <9d7e85914eb1cdb313b28cb019093a84dd9b4773.1703167505.git.michal.simek@amd.com>


On Thu, 21 Dec 2023 15:05:09 +0100, 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
> 

Reviewed-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2023-12-21 21:11 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 [this message]
2023-12-22  8:20 ` Krzysztof Kozlowski
2024-01-02 15:32   ` Michal Simek
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=170319311633.101509.1532196763061569676.robh@kernel.org \
    --to=robh@kernel.org \
    --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=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --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