From: "Friday Yang (杨阳)" <Friday.Yang@mediatek.com>
To: "conor@kernel.org" <conor@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Garmin Chang (張家銘)" <Garmin.Chang@mediatek.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Yong Wu (吴勇)" <Yong.Wu@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: clock: mediatek: Add SMI LARBs reset for MT8188
Date: Wed, 22 Jan 2025 07:40:12 +0000 [thread overview]
Message-ID: <2bfb6c05a3471e54f51c06895709853661e82c9a.camel@mediatek.com> (raw)
In-Reply-To: <20250121-violet-widely-df3567b085a4@spud>
On Tue, 2025-01-21 at 17:30 +0000, Conor Dooley wrote:
> On Tue, Jan 21, 2025 at 02:50:40PM +0800, Friday Yang wrote:
> > SMI LARBs require reset functions when applying clamp operations.
> > Add '#reset-cells' for the clock controller located in image,
> > camera
> > and IPE subsystems.
>
> A new required property is an abi break, please explain why this is
> required. What are "SMI LARBs"? Why did things previously work
> without
> acting as a reset controller?
>
The background can refer to the discussion in the following link:
https://lore.kernel.org/all/CAFGrd9qZhObQXvm2_abqaX83xMLqxjQETB2=wXpobDWU1CnvkA@mail.gmail.com/
https://lore.kernel.org/all/CAPDyKFpokXV2gJDgowbixTvOH_5VL3B5H8eyhP+KJ5Fasm2rFg@mail.gmail.com/
SMI clamp and reset operations should be implemented in SMI driver
instead of PM driver.
I previously added the SMI reset control driver. However, the
reviewer's comments are correct, these functions have already
been implemented in the clock control driver. There is no need
to submit duplicate code.
https://lore.kernel.org/lkml/20241120063305.8135-2-friday.yang@mediatek.com/
https://lore.kernel.org/lkml/20241120063305.8135-3-friday.yang@mediatek.com/
On the MediaTek platform, the SMI block diagram like this:
DRAM
|
EMI(External Memory Interface)
| |
MediaTek IOMMU(Input Output Memory Management Unit)
| |
SMI-Common(Smart Multimedia Interface Common)
|
+----------------+------------------+
| | |
| | |
| | |
| | |
| | |
larb0 SMI-Sub-Common0 SMI-Sub-Common1
| | | | |
larb1 larb2 larb3 larb7 larb9
The SMI-Common connects with SMI LARBs and IOMMU. The maximum LARBs
number that connects with a SMI-Common is 8. If the engines number is
over 8, sometimes we use a SMI-Sub-Common which is nearly same with
SMI-Common. It supports up to 8 input and 1 output(SMI-Common has 2
output).
> >
> > Signed-off-by: Friday Yang <friday.yang@mediatek.com>
> > ---
> > .../bindings/clock/mediatek,mt8188-clock.yaml | 21
> > +++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/clock/mediatek,mt8188-
> > clock.yaml
> > b/Documentation/devicetree/bindings/clock/mediatek,mt8188-
> > clock.yaml
> > index 860570320545..2985c8c717d7 100644
> > --- a/Documentation/devicetree/bindings/clock/mediatek,mt8188-
> > clock.yaml
> > +++ b/Documentation/devicetree/bindings/clock/mediatek,mt8188-
> > clock.yaml
> > @@ -57,6 +57,27 @@ required:
> > - reg
> > - '#clock-cells'
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - mediatek,mt8188-camsys-rawa
> > + - mediatek,mt8188-camsys-rawb
> > + - mediatek,mt8188-camsys-yuva
> > + - mediatek,mt8188-camsys-yuvb
> > + - mediatek,mt8188-imgsys-wpe1
> > + - mediatek,mt8188-imgsys-wpe2
> > + - mediatek,mt8188-imgsys-wpe3
> > + - mediatek,mt8188-imgsys1-dip-nr
> > + - mediatek,mt8188-imgsys1-dip-top
> > + - mediatek,mt8188-ipesys
> > +
> > + then:
> > + required:
> > + - '#reset-cells'
> > +
> > additionalProperties: false
> >
> > examples:
> > --
> > 2.46.0
> >
next prev parent reply other threads:[~2025-01-22 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 6:50 [PATCH v3 0/2] Add SMI LARBs reset for MediaTek MT8188 SoC Friday Yang
2025-01-21 6:50 ` [PATCH v3 1/2] dt-bindings: clock: mediatek: Add SMI LARBs reset for MT8188 Friday Yang
2025-01-21 17:30 ` Conor Dooley
2025-01-22 7:40 ` Friday Yang (杨阳) [this message]
2025-01-24 17:31 ` Conor Dooley
2025-02-18 12:44 ` Friday Yang (杨阳)
2025-02-18 14:24 ` AngeloGioacchino Del Regno
2025-02-18 16:53 ` Conor Dooley
2025-01-21 6:50 ` [PATCH v3 2/2] clk: " Friday Yang
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=2bfb6c05a3471e54f51c06895709853661e82c9a.camel@mediatek.com \
--to=friday.yang@mediatek.com \
--cc=Garmin.Chang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Yong.Wu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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