From: andrew-sh.cheng <andrew-sh.cheng@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] arm64: dts: mediatek: add cpufreq and cci devfreq nodes for mt8183
Date: Mon, 25 May 2020 10:21:29 +0800 [thread overview]
Message-ID: <1590373289.12854.3.camel@mtksdaap41> (raw)
In-Reply-To: <085be59e-76d5-4743-0f0c-12f6440715fe@gmail.com>
On Sat, 2020-05-23 at 21:04 +0200, Matthias Brugger wrote:
>
> On 20/12/2019 08:26, Andrew-sh.Cheng wrote:
> > From: "Andrew-sh.Cheng" <andrew-sh.cheng@mediatek.com>
> >
> > add cpufreq and cci devfreq nodes for mt8183
> >
> > Depend on regulator node patch:
> > https://patchwork.kernel.org/patch/11284617/
> >
> > Signed-off-by: Andrew-sh.Cheng <andrew-sh.cheng@mediatek.com>
> > ---
> > arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 36 ++++
> > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 245 ++++++++++++++++++++++++++++
> > 2 files changed, 281 insertions(+)
> >
> [...]
> > +
> > + cci: cci {
> > + compatible = "mediatek,mt8183-cci";
>
> I wasn't able to find anyprovider for this compatible.
>
> I'll drop this patch from my queue.
>
> Regards,
> Matthias
Hi Matthias,
I put the dt-binding at another patch set.
https://patchwork.kernel.org/patch/11559265/
I will integrate this patch with that patch set and resend.
Thank you.
BR
Andrew-sh.Cheng
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-05-25 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 7:26 [PATCH V3] arm64: dts: mediatek: add cpufreq and cci devfreq nodes for mt8183 Andrew-sh.Cheng
2020-05-21 10:25 ` Matthias Brugger
2020-05-23 19:04 ` Matthias Brugger
2020-05-25 2:21 ` andrew-sh.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=1590373289.12854.3.camel@mtksdaap41 \
--to=andrew-sh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@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).