linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Romain Perier <romain.perier@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: devicetree <devicetree@vger.kernel.org>,
	linux-serial@vger.kernel.org,  Rob Herring <robh+dt@kernel.org>,
	andriy.shevchenko@linux.intel.com,
	 Jiri Slaby <jirislaby@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/4] ARM: dts: mstar: Switch pm_uart to mstar,msc313-uart
Date: Fri, 25 Mar 2022 13:23:14 +0100	[thread overview]
Message-ID: <CABgxDoLg4cf8qGVAhnp4Tj1cWZ0X+vM0ueTy2wp68BbgRLGuNQ@mail.gmail.com> (raw)
In-Reply-To: <20220324124402.3631379-4-daniel@0x0f.com>

Hi Daniel,

Le jeu. 24 mars 2022 à 13:44, Daniel Palmer <daniel@0x0f.com> a écrit :
>
> The UART used in these SoCs is actually a variant of the dw apb uart.
> Now there is a compatible string in that driver to handle the quirks
> switch the compatible for pm_uart over to mstar,msc313-uart.
>
> Signed-off-by: Daniel Palmer <daniel@0x0f.com>
Reviewed-by: Romain Perier <romain.perier@gmail.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-25 12:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 12:43 [PATCH 0/4] Add support for MStar MSC313 uarts Daniel Palmer
2022-03-24 12:43 ` [PATCH 1/4] dt-bindings: serial: snps-dw-apb-uart: Add " Daniel Palmer
2022-04-01  0:20   ` Rob Herring
2022-03-24 12:44 ` [PATCH 2/4] serial: 8250_dw: Add MStar MSC313 quirk Daniel Palmer
2022-03-24 13:58   ` Andy Shevchenko
2022-03-24 12:44 ` [PATCH 3/4] ARM: dts: mstar: Switch pm_uart to mstar,msc313-uart Daniel Palmer
2022-03-25 12:23   ` Romain Perier [this message]
2022-03-24 12:44 ` [PATCH 4/4] ARM: dts: mstar: Add second UART to base dtsi Daniel Palmer
2022-03-25 12:25   ` Romain Perier
2022-03-28 13:28   ` 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=CABgxDoLg4cf8qGVAhnp4Tj1cWZ0X+vM0ueTy2wp68BbgRLGuNQ@mail.gmail.com \
    --to=romain.perier@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).