From: "Moudy Ho (何宗原)" <Moudy.Ho@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v5 01/10] dt-bindings: arm: mediatek: migrate MT8195 vppsys0/1 to mtk-mmsys driver
Date: Mon, 16 Jan 2023 09:08:31 +0000 [thread overview]
Message-ID: <de1f1e594477e72e308f8f6f4392ef16b2d59cc9.camel@mediatek.com> (raw)
In-Reply-To: <ce4d2d3b-a826-ac59-e077-2fa452d115a3@linaro.org>
On Mon, 2023-01-16 at 09:00 +0100, Krzysztof Kozlowski wrote:
> On 16/01/2023 03:42, Moudy Ho (何宗原) wrote:
> > On Fri, 2023-01-13 at 12:58 +0100, Krzysztof Kozlowski wrote:
> > > On 13/01/2023 06:42, Moudy Ho wrote:
> > > > MT8195 vppsys0/1 should be probed from mtk-mmsys driver to
> > > > populate device by platform_device_register_data then start
> > > > its own clock driver.
> > >
> > > Unfortunately I don't understand why this justifies removal of
> > > compatibles.
> > >
> > > How do you propagate or instantiate devices is not really
> > > connected
> > > with
> > > the hardware description.
> > >
> > > Best regards,
> > > Krzysztof
> > >
> >
> > Hi Krzysztof,
> >
> > Refer to the comments of 0/8 and 1/8 in the following series:
> >
https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=702518__;!!CTRNKA9wMg0ARbw!iR9oqyYsBrujnl_v5DEuDZrTGp75iBKkLK99KWQV391krqpZ_lK3d2Yr9MKxgROBuVgq2fnV9cFs7jzGwRjYX5_zjL0o$
> >
> >
> > This patch is used in conjunction with another one(Message ID =
> > 20230113054304.21841-7-moudy.ho@mediatek.com/) to fix the binding
> > warnings caused by newly added in MMSYS.
>
> The patch should stand on its own. IOW, it should explain everything
> needed and it should justify its existence.
>
> Best regards,
> Krzysztof
>
Hi Krzysztof,
Thanks for the suggestion, I will split all related patches into
another series.
Sincerely,
Moudy
next prev parent reply other threads:[~2023-01-16 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 5:42 [PATCH v5 00/10] add support for MT8195 VPPSYS on MMSYS and MUTEX Moudy Ho
2023-01-13 5:42 ` [PATCH v5 01/10] dt-bindings: arm: mediatek: migrate MT8195 vppsys0/1 to mtk-mmsys driver Moudy Ho
2023-01-13 11:58 ` Krzysztof Kozlowski
2023-01-16 2:42 ` Moudy Ho (何宗原)
2023-01-16 8:00 ` Krzysztof Kozlowski
2023-01-16 9:08 ` Moudy Ho (何宗原) [this message]
2023-01-13 5:42 ` [PATCH v5 02/10] dt-bindings: arm: mediatek: mmsys: Add support for MT8195 VPPSYS Moudy Ho
2023-01-13 11:59 ` Krzysztof Kozlowski
2023-01-16 2:49 ` Moudy Ho (何宗原)
2023-01-13 5:42 ` [PATCH v5 03/10] dt-bindings: soc: mediatek: " Moudy Ho
2023-01-13 5:42 ` [PATCH v5 04/10] arm64: dts: mediatek: mt8195: add MMSYS configuration for VPPSYS Moudy Ho
2023-01-13 5:42 ` [PATCH v5 05/10] arm64: dts: mediatek: mt8195: add MUTEX " Moudy Ho
2023-01-13 5:43 ` [PATCH v5 06/10] clk: mediatek: remove MT8195 vppsys/0/1 simple_probe Moudy Ho
2023-01-13 5:43 ` [PATCH v5 07/10] soc: mediatek: mmsys: add support for MT8195 VPPSYS Moudy Ho
2023-01-13 5:43 ` [PATCH v5 08/10] soc: mediatek: mmsys: add config api for RSZ switching and DCM Moudy Ho
2023-01-13 5:43 ` [PATCH v5 09/10] soc: mediatek: mutex: Add mtk_mutex_set_mod support to set MOD1 Moudy Ho
2023-01-13 5:43 ` [PATCH v5 10/10] soc: mediatek: mutex: support MT8195 VPPSYS Moudy Ho
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=de1f1e594477e72e308f8f6f4392ef16b2d59cc9.camel@mediatek.com \
--to=moudy.ho@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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=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