linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: krzysztof.kozlowski@canonical.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, jirislaby@kernel.org,
	kernel@axis.com, linux-kernel@vger.kernel.org,
	alim.akhtar@samsung.com, linux-serial@vger.kernel.org,
	robh+dt@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 1/2] dt-bindings: serial: samsung: Add ARTPEC-8 UART
Date: Fri, 11 Mar 2022 08:52:45 -0600	[thread overview]
Message-ID: <YitiPSZp4thtal8D@robh.at.kernel.org> (raw)
In-Reply-To: <20220311094515.3223023-2-vincent.whitchurch@axis.com>

On Fri, 11 Mar 2022 10:45:14 +0100, Vincent Whitchurch wrote:
> Add a compatible for the UART on the ARTPEC-8 SoC.  This hardware block
> is closely related to the variants used on the Exynos chips.  The
> register layout is identical to Exynos850 et al but the fifo size is
> different (64 bytes in each direction for all instances).
> 
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> 
> Notes:
>     v2:
>     - Expand commit message.
>     - Define required clocks.
> 
>  Documentation/devicetree/bindings/serial/samsung_uart.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 

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

  parent reply	other threads:[~2022-03-11 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  9:45 [PATCH v2 0/2] Add support for ARTPEC-8 UART Vincent Whitchurch
2022-03-11  9:45 ` [PATCH v2 1/2] dt-bindings: serial: samsung: Add " Vincent Whitchurch
2022-03-11 10:40   ` Krzysztof Kozlowski
2022-03-11 14:52   ` Rob Herring [this message]
2022-03-11  9:45 ` [PATCH v2 2/2] tty: serial: samsung: Add ARTPEC-8 support Vincent Whitchurch
2022-03-11 10:42   ` Krzysztof Kozlowski
2022-03-11 10:44     ` Krzysztof Kozlowski

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=YitiPSZp4thtal8D@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kernel@axis.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vincent.whitchurch@axis.com \
    /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).