From: "Rafał Miłecki" <zajec5@gmail.com>
To: Tinghan Shen <tinghan.shen@mediatek.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sean Wang <sean.wang@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-mediatek <linux-mediatek@lists.infradead.org>
Subject: Duplicated bindings for mediatek,mt8173-scpsys
Date: Fri, 28 Jun 2024 09:57:07 +0200 [thread overview]
Message-ID: <7614ed44-7613-4912-9b4b-62c92abbc9bd@gmail.com> (raw)
I noticed that "mediatek,mt8173-scpsys" compatible is specified in two
places:
Documentation/devicetree/bindings/soc/mediatek/scpsys.txt
Documentation/devicetree/bindings/mfd/mediatek,mt8195-scpsys.yaml
The first one seems to be "real" hardware block. It also has a Linux
driver at drivers/pmdomain/mediatek/mtk-scpsys.c . It also seems that
scpsys.txt was first added explicitly for MT8173.
The later one seems to be "just" an MFD with no real driver but it
seems to be actually used in arch/arm64/boot/dts/mediatek/mt8173.dtsi .
Can I ask for some assistance sorting this out?
Relevant kernel commits:
commit 26331d261f49949bff6477fc9c844b17076fa245
Author: Tinghan Shen <tinghan.shen@mediatek.com>
Date: Thu Aug 11 10:57:59 2022 +0800
dt-bindings: mfd: mt8195: Add bindings for MediaTek SCPSYS
commit c84e358718a66f76ac0de1681d15d8d0c68fcdab
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Wed Jun 24 08:17:04 2015 +0200
soc: Mediatek: Add SCPSYS power domain driver
commit 859e42800bcfc4db9cefaa2c24d6e3a203fe961d
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Wed Jun 24 08:17:03 2015 +0200
dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit
next reply other threads:[~2024-06-28 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 7:57 Rafał Miłecki [this message]
2024-07-02 1:58 ` Duplicated bindings for mediatek,mt8173-scpsys TingHan Shen (沈廷翰)
2024-07-02 12:12 ` AngeloGioacchino Del Regno
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=7614ed44-7613-4912-9b4b-62c92abbc9bd@gmail.com \
--to=zajec5@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sean.wang@mediatek.com \
--cc=tinghan.shen@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).