Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: allen-kh.cheng <allen-kh.cheng@mediatek.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Ryder Lee <ryder.lee@kernel.org>, <hsinyi@chromium.org>
Subject: Re: [PATCH v8 2/2] arm64: dts: Add MediaTek SoC MT8186 dts and evaluation board and Makefile
Date: Thu, 5 May 2022 20:21:20 +0800	[thread overview]
Message-ID: <9f0d1d279c838bc46d499aa020a6b47a8a25f6f4.camel@mediatek.com> (raw)
In-Reply-To: <20220429213907.d2lwnukugoa7owxn@notapiano>

On Fri, 2022-04-29 at 17:39 -0400, Nícolas F. R. A. Prado wrote:
> On Thu, Apr 28, 2022 at 01:27:41PM -0400, Nícolas F. R. A. Prado
> wrote:
> > Hi Allen,
> > 
> > On Thu, Apr 28, 2022 at 02:17:17PM +0800, Allen-KH Cheng wrote:
> > > +		scp: scp@10500000 {
> > > +			compatible = "mediatek,mt8186-scp";
> > > +			reg = <0 0x10500000 0 0x40000>,
> > > +			      <0 0x105c0000 0 0x19080>;
> > > +			reg-names = "sram", "cfg";
> > 
> > The mtk,scp dt-binding should be updated as it currently doesn't
> > allow l1tcm to
> > be missing. According to comments in the driver cfg is optional as
> > well, so a
> > patch to the binding making both optional would be great.
> 
> Hi Allen,
> 
> actually I've just sent a patch for this myself [1], as it was also
> required for
> mt8192-asurada. Sorry for the noise.
> 
> Thanks,
> Nícolas
> 
> [1] 
> https://lore.kernel.org/all/20220429211111.2214119-2-nfraprado@collabora.com/
> 

Hi Nícolas,

I think I can remove scp node in next version and update this in
another PATCH for [1]. 

thanks,

> > 
> > Thanks,
> > Nícolas


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      reply	other threads:[~2022-05-05 12:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:17 [PATCH v8 0/2] Add basic node support for MediaTek MT8186 SoC Allen-KH Cheng
2022-04-28  6:17 ` [PATCH v8 1/2] dt-bindings: arm: Add compatible for MediaTek MT8186 Allen-KH Cheng
2022-04-28 13:34   ` AngeloGioacchino Del Regno
2022-04-29 22:31   ` Rob Herring
2022-04-28  6:17 ` [PATCH v8 2/2] arm64: dts: Add MediaTek SoC MT8186 dts and evaluation board and Makefile Allen-KH Cheng
2022-04-28 13:32   ` AngeloGioacchino Del Regno
2022-05-05 13:10     ` allen-kh.cheng
2022-04-28 17:27   ` Nícolas F. R. A. Prado
2022-04-29 21:39     ` Nícolas F. R. A. Prado
2022-05-05 12:21       ` allen-kh.cheng [this message]

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=9f0d1d279c838bc46d499aa020a6b47a8a25f6f4.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsinyi@chromium.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nfraprado@collabora.com \
    --cc=robh+dt@kernel.org \
    --cc=ryder.lee@kernel.org \
    --cc=wenst@chromium.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