From: Conor Dooley <conor@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: peter.wang@mediatek.com, linux-kernel@vger.kernel.org,
robh@kernel.org, krzysztof.kozlowski@linaro.org,
conor+dt@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
wsd_upstream@mediatek.com, linux-mediatek@lists.infradead.org,
linux-devicetree@vger.kernel.org, chun-hung.wu@mediatek.com,
alice.chao@mediatek.com, naomi.chu@mediatek.com,
ed.tsai@mediatek.com
Subject: Re: [PATCH v1 1/2] Documentation: dt: reset: add mediatek,syscon-reset binding
Date: Fri, 26 Jun 2026 16:53:28 +0100 [thread overview]
Message-ID: <20260626-rewrap-sediment-ad9449abd837@spud> (raw)
In-Reply-To: <4ac862d82690a850eeaa997f041f22ee61233ed7.camel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Fri, Jun 26, 2026 at 10:33:20AM +0200, Philipp Zabel wrote:
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + ufs0cfg_ao: syscon@16840000 {
> > + compatible = "mediatek,mt8183-ufs0cfg_ao", "syscon", "simple-mfd";
>
> Where is the binding doc for mediatek,mt8183-ufs0cfg_ao? Is this
> simple-mfd just to load the reset driver?
It isn't going to exist, since we will chuck a fit at the underscore!
>
> > + reg = <0x16840000 0x1000>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > +
> > + ufs0cfgao_rst: reset-controller {
> > + compatible = "mediatek,syscon-reset";
>
> It looks to me like this is just two registers inside ufs0cfg_ao, not a
> separate device. Why don't you just add #reset-cells to the parent
> node?
I concur, seems like it should be in the parent.
pw-bot: changes-requested
>
> > + #reset-cells = <1>;
> > + mediatek,reset-bits =
> > + <0x48 3 0x4c 3 100>,
> > + <0x148 0 0x14c 0 100>,
> > + <0x148 1 0x14c 1 100>,
> > + <0x148 2 0x14c 2 0>;
> > + };
>
> Why is this in DT? This should be a table in the reset driver.
>
> regards
> Philipp
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-26 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 7:46 [PATCH v1 0/2] reset: mediatek: add syscon-based reset controller peter.wang
2026-06-26 7:46 ` [PATCH v1 1/2] Documentation: dt: reset: add mediatek,syscon-reset binding peter.wang
2026-06-26 8:33 ` Philipp Zabel
2026-06-26 15:53 ` Conor Dooley [this message]
2026-07-01 6:36 ` Peter Wang (王信友)
2026-07-01 6:35 ` Peter Wang (王信友)
2026-07-01 16:57 ` Conor Dooley
2026-07-02 8:52 ` Peter Wang (王信友)
2026-07-02 18:44 ` Conor Dooley
2026-07-02 8:55 ` AngeloGioacchino Del Regno
2026-07-02 9:39 ` Peter Wang (王信友)
2026-07-03 9:21 ` Philipp Zabel
2026-06-26 7:46 ` [PATCH v1 2/2] reset: mediatek: add syscon-based reset controller driver peter.wang
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=20260626-rewrap-sediment-ad9449abd837@spud \
--to=conor@kernel.org \
--cc=alice.chao@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chun-hung.wu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=ed.tsai@mediatek.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=naomi.chu@mediatek.com \
--cc=p.zabel@pengutronix.de \
--cc=peter.wang@mediatek.com \
--cc=robh@kernel.org \
--cc=wsd_upstream@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