From: <xinlei.lee@mediatek.com>
To: <thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
<lee.jones@linaro.org>, <robh+dt@kernel.org>,
<matthias.bgg@gmail.com>
Cc: <linux-pwm@vger.kernel.org>, <linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<rex-bc.chen@mediatek.com>, <jitao.shi@mediatek.com>,
Xinlei Lee <xinlei.lee@mediatek.com>
Subject: [PATCH v5,0/4] Convert pwm-mtk-disp.txt to mediatek, pwm-disp.yaml format
Date: Thu, 31 Mar 2022 20:47:49 +0800 [thread overview]
Message-ID: <1648730873-18505-1-git-send-email-xinlei.lee@mediatek.com> (raw)
From: Xinlei Lee <xinlei.lee@mediatek.com>
Changes since v4:
1.Base on Linux-next.
2.Cancel removal of mt8167 compatiable patch.
Changes since v3:
1. Combine multiplexed socs into one entry
Changes since v2:
1. Modify the PWM name to DISP_PWM.
2. Include pwm.yaml.
3. Separate conversion files and add/remove operations.
Changes since v1:
1. Fixed formatting issues mentioned in the v1.
2. Delete pwm-mtk-disp.txt.
3. Add mtk_pwm dt_maintainers.
4. Add "#pwm-cells" & power-domains properties.
5. Make dt_checking successful.
Xinlei Lee (4):
dt-bindings: pwm: Convert pwm-mtk-disp.txt to mediatek,pwm-disp.yaml
format
dt-bindings: pwm: Add compatible for MediaTek MT8192
dt-bindings: pwm: Add compatible for MediaTek MT8195
dt-bindings: pwm: Add compatible for MediaTek MT8186
.../bindings/pwm/mediatek,pwm-disp.yaml | 72 +++++++++++++++++++
.../devicetree/bindings/pwm/pwm-mtk-disp.txt | 45 ------------
2 files changed, 72 insertions(+), 45 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pwm/mediatek,pwm-disp.yaml
delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-mtk-disp.txt
--
2.18.0
next reply other threads:[~2022-03-31 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:47 xinlei.lee [this message]
2022-03-31 12:47 ` [PATCH v5,1/4] dt-bindings: pwm: Convert pwm-mtk-disp.txt to mediatek,pwm-disp.yaml format xinlei.lee
2022-03-31 14:03 ` [PATCH v5, 1/4] dt-bindings: pwm: Convert pwm-mtk-disp.txt to mediatek, pwm-disp.yaml format AngeloGioacchino Del Regno
2022-03-31 23:20 ` [PATCH v5,1/4] dt-bindings: pwm: Convert pwm-mtk-disp.txt to mediatek,pwm-disp.yaml format Miles Chen
2022-03-31 12:47 ` [PATCH v5,2/4] dt-bindings: pwm: Add compatible for MediaTek MT8192 xinlei.lee
2022-03-31 14:03 ` AngeloGioacchino Del Regno
2022-03-31 20:25 ` Krzysztof Kozlowski
2022-03-31 12:47 ` [PATCH v5,3/4] dt-bindings: pwm: Add compatible for MediaTek MT8195 xinlei.lee
2022-03-31 14:04 ` AngeloGioacchino Del Regno
2022-03-31 20:25 ` Krzysztof Kozlowski
2022-03-31 12:47 ` [PATCH v5 4/4] dt-bindings: pwm: Add compatible for MediaTek MT8186 xinlei.lee
2022-03-31 14:03 ` AngeloGioacchino Del Regno
2022-03-31 20:26 ` Krzysztof Kozlowski
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=1648730873-18505-1-git-send-email-xinlei.lee@mediatek.com \
--to=xinlei.lee@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jitao.shi@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).