From: Matthias Brugger <matthias.bgg@gmail.com>
To: Fabien Parent <fparent@baylibre.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org
Cc: robh+dt@kernel.org, vkoul@kernel.org, sean.wang@mediatek.com
Subject: Re: [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC
Date: Mon, 19 Oct 2020 12:24:40 +0200 [thread overview]
Message-ID: <9308a487-ed84-6112-d612-a8a777ee0dee@gmail.com> (raw)
In-Reply-To: <20201015123315.334919-1-fparent@baylibre.com>
On 15/10/2020 14:33, Fabien Parent wrote:
> Add bindings to APDMA for MT8516 SoC. MT8516 is compatible with MT6577.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt b/Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt
> index 2117db0ce4f2..fef9c1eeb264 100644
> --- a/Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt
> +++ b/Documentation/devicetree/bindings/dma/mtk-uart-apdma.txt
> @@ -4,6 +4,7 @@ Required properties:
> - compatible should contain:
> * "mediatek,mt2712-uart-dma" for MT2712 compatible APDMA
> * "mediatek,mt6577-uart-dma" for MT6577 and all of the above
> + * "mediatek,mt8516-uart-dma", "mediatek,mt6577" for MT8516 SoC
>
> - reg: The base address of the APDMA register bank.
>
>
next prev parent reply other threads:[~2020-10-19 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 12:33 [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC Fabien Parent
2020-10-15 12:33 ` [PATCH 2/2] arm64: dts: mediatek: mt8516: add support for APDMA Fabien Parent
2020-10-19 10:24 ` Matthias Brugger [this message]
2020-10-19 21:16 ` [PATCH 1/2] dt-bindings: dma: mtk-apdma: add bindings for MT8516 SOC Rob Herring
2020-11-27 8:46 ` Matthias Brugger
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=9308a487-ed84-6112-d612-a8a777ee0dee@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vkoul@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).