From: Matthias Brugger <matthias.bgg@gmail.com>
To: Erin Lo <erin.lo@mediatek.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: devicetree@vger.kernel.org,
srv_heupstream <srv_heupstream@mediatek.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, yingjoe.chen@mediatek.com,
mars.cheng@mediatek.com, eddie.huang@mediatek.com,
linux-clk@vger.kernel.org, zhiyong.tao@mediatek.com,
Mengqi.Zhang@mediatek.com
Subject: Re: [PATCH v8 1/2] dt-bindings: serial: Add compatible for Mediatek MT8183
Date: Tue, 12 Mar 2019 15:41:57 +0100 [thread overview]
Message-ID: <d824b15d-49b4-ef6c-779a-0c21c8c05d62@gmail.com> (raw)
In-Reply-To: <1552294472-32929-2-git-send-email-erin.lo@mediatek.com>
On 11/03/2019 09:54, Erin Lo wrote:
> This adds dt-binding documentation of uart for Mediatek MT8183 SoC
> Platform.
>
> Signed-off-by: Erin Lo <erin.lo@mediatek.com>
> Acked-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/serial/mtk-uart.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/serial/mtk-uart.txt b/Documentation/devicetree/bindings/serial/mtk-uart.txt
> index 742cb47..bcfb131 100644
> --- a/Documentation/devicetree/bindings/serial/mtk-uart.txt
> +++ b/Documentation/devicetree/bindings/serial/mtk-uart.txt
> @@ -16,6 +16,7 @@ Required properties:
> * "mediatek,mt8127-uart" for MT8127 compatible UARTS
> * "mediatek,mt8135-uart" for MT8135 compatible UARTS
> * "mediatek,mt8173-uart" for MT8173 compatible UARTS
> + * "mediatek,mt8183-uart", "mediatek,mt6577-uart" for MT8183 compatible UARTS
> * "mediatek,mt6577-uart" for MT6577 and all of the above
>
> - reg: The base address of the UART register bank.
>
Acked-by: Matthias Brugger <matthias.bgg@gmail.com>
Greg will you take this through your branch or do you prefer me to queue it?
Regards,
Matthias
next prev parent reply other threads:[~2019-03-12 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 8:54 [PATCH v8 0/2] Add basic and clock support for Mediatek MT8183 SoC Erin Lo
2019-03-11 8:54 ` [PATCH v8 1/2] dt-bindings: serial: Add compatible for Mediatek MT8183 Erin Lo
2019-03-12 14:41 ` Matthias Brugger [this message]
2019-03-12 16:33 ` Greg Kroah-Hartman
2019-03-11 8:54 ` [PATCH v8 2/2] arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile Erin Lo
2019-03-12 12:22 ` Matthias Brugger
2019-03-13 8:26 ` Erin Lo
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=d824b15d-49b4-ef6c-779a-0c21c8c05d62@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Mengqi.Zhang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mars.cheng@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@mediatek.com \
--cc=tglx@linutronix.de \
--cc=yingjoe.chen@mediatek.com \
--cc=zhiyong.tao@mediatek.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).