From: Macpaul Lin <macpaul.lin@mediatek.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <linux-leds@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Sean Wang <sean.wang@mediatek.com>, Lee Jones <lee@kernel.org>,
Alexandre Mergnat <amergnat@baylibre.com>,
Flora Fu <flora.fu@mediatek.com>
Cc: Bear Wang <bear.wang@mediatek.com>,
Pablo Sun <pablo.sun@mediatek.com>,
Macpaul Lin <macpaul.lin@mediatek.com>,
Macpaul Lin <macpaul@gmail.com>, Sen Chu <sen.chu@mediatek.com>,
Chris-qj chen <chris-qj.chen@mediatek.com>,
MediaTek Chromebook Upstream
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <linux-pm@vger.kernel.org>,
<linux-rtc@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<devicetree@vger.kernel.org>, Chen-Yu Tsai <wenst@chromium.org>
Subject: [PATCH v2 3/7] dt-bindings: rtc: mt6397: merge to MFD mediatek,mt6397 DT schema
Date: Fri, 30 Aug 2024 19:07:28 +0800 [thread overview]
Message-ID: <20240830110732.30080-3-macpaul.lin@mediatek.com> (raw)
In-Reply-To: <20240830110732.30080-1-macpaul.lin@mediatek.com>
Convert rtc-mt6397.txt be compatible with the DT schema.
Since this is a simple RTC device node, merge it into parent
mediatek,mt6397.yaml. Subsequently, remove rtc-mt6397.txt with a
separate patch.
Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>
---
.../devicetree/bindings/rtc/rtc-mt6397.txt | 31 -------------------
1 file changed, 31 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt6397.txt
Changes for v1 and v2:
- This is the first version of converting rtc-mt6397.txt.
This is because converting rtc-mt6397 together
with mfd/mediatek,mt6397.yaml, so we've create a patch set
instead of submitting single patch for each subdevice.
- This patch has been made base on linux-next/master git repo.
diff --git a/Documentation/devicetree/bindings/rtc/rtc-mt6397.txt b/Documentation/devicetree/bindings/rtc/rtc-mt6397.txt
deleted file mode 100644
index 7212076..0000000
--- a/Documentation/devicetree/bindings/rtc/rtc-mt6397.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-Device-Tree bindings for MediaTek PMIC based RTC
-
-MediaTek PMIC based RTC is an independent function of MediaTek PMIC that works
-as a type of multi-function device (MFD). The RTC can be configured and set up
-with PMIC wrapper bus which is a common resource shared with the other
-functions found on the same PMIC.
-
-For MediaTek PMIC MFD bindings, see:
-../mfd/mt6397.txt
-
-For MediaTek PMIC wrapper bus bindings, see:
-../soc/mediatek/pwrap.txt
-
-Required properties:
-- compatible: Should be one of follows
- "mediatek,mt6323-rtc": for MT6323 PMIC
- "mediatek,mt6358-rtc": for MT6358 PMIC
- "mediatek,mt6366-rtc", "mediatek,mt6358-rtc": for MT6366 PMIC
- "mediatek,mt6397-rtc": for MT6397 PMIC
-
-Example:
-
- pmic {
- compatible = "mediatek,mt6323";
-
- ...
-
- rtc {
- compatible = "mediatek,mt6323-rtc";
- };
- };
--
2.45.2
next prev parent reply other threads:[~2024-08-30 11:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 11:07 [PATCH v2 1/7] regulator: dt-bindings: mt6323: Convert to DT schema Macpaul Lin
2024-08-30 11:07 ` [PATCH v2 2/7] dt-bindings: mfd: mediatek: mt6397: Convert to DT schema format Macpaul Lin
2024-08-30 12:29 ` Rob Herring (Arm)
2024-08-30 15:33 ` Rob Herring
2024-09-13 18:15 ` Macpaul Lin
2024-08-31 7:04 ` kernel test robot
2024-08-30 11:07 ` Macpaul Lin [this message]
2024-08-30 15:34 ` [PATCH v2 3/7] dt-bindings: rtc: mt6397: merge to MFD mediatek,mt6397 DT schema Rob Herring
2024-09-13 16:29 ` Macpaul Lin
2024-08-30 11:07 ` [PATCH v2 4/7] regulator: dt-bindings: mt6397: move examples to parent PMIC mt6397 Macpaul Lin
2024-08-30 11:07 ` [PATCH v2 5/7] dt-bindings: leds: mt6323: merge to MFD mediatek,mt6397 DT schema Macpaul Lin
2024-08-31 8:06 ` kernel test robot
2024-08-30 11:07 ` [PATCH v2 6/7] dt-bindings: power: reset: " Macpaul Lin
2024-09-03 21:42 ` Sebastian Reichel
2024-09-13 16:33 ` Macpaul Lin
2024-08-30 11:07 ` [PATCH v2 7/7] dt-bindings: sound: mt6358: " Macpaul Lin
2024-08-30 12:29 ` [PATCH v2 1/7] regulator: dt-bindings: mt6323: Convert to " Rob Herring (Arm)
2024-08-30 14:50 ` Rob Herring
2024-09-13 17:47 ` Macpaul Lin
2024-08-31 5:51 ` kernel test robot
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=20240830110732.30080-3-macpaul.lin@mediatek.com \
--to=macpaul.lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bear.wang@mediatek.com \
--cc=broonie@kernel.org \
--cc=chris-qj.chen@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=flora.fu@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=macpaul@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=pablo.sun@mediatek.com \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sen.chu@mediatek.com \
--cc=sre@kernel.org \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).