From: Jitao Shi <jitao.shi@mediatek.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: <linux-pwm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <srv_heupstream@mediatek.com>,
<yingjoe.chen@mediatek.com>, <eddie.huang@mediatek.com>,
<ck.hu@mediatek.com>, <stonea168@163.com>,
<huijuan.xie@mediatek.com>, <shuijing.li@mediatek.com>,
Jitao Shi <jitao.shi@mediatek.com>
Subject: [PATCH v6 0/5] fix the clks on/off mismatch issue and switch pwm-mtk-disp to atomic APIs
Date: Sat, 24 Jul 2021 16:18:44 +0800 [thread overview]
Message-ID: <20210724081849.182108-1-jitao.shi@mediatek.com> (raw)
Changes since v5:
- fix overflow.
- Seperate the reg shadow as a single patch.
Changes since v4:
- Squash the commit "move the commit to clock enabled" to "adjust the clocks to avoid them mismatch".
- Drop the useless comment about MT2701.
- Reenable the clks "mm" and "main" in .enable().
- Fix typo.
- Seperate get_state() operation as single patch.
Changes since v3:
- Seperate the clock sequence as single patch.
- Fixup the reg commit when clocks sequence changed.
- Merge the apply and get_state as single patch.
Changes since v2:
- Change commit messages to remove the clock operations for atomic APIs.
- Rebase to v5.13 rc1.
Changes since v1:
- Seperate clock operation as single patch.
- Seperate apply() as single patch.
- Seperate get_state() operation as single patch.
Jitao Shi (5):
pwm: mtk-disp: adjust the clocks to avoid them mismatch
pwm: mtk_disp: fix force reg to working reg.
pwm: mtk_disp: implement atomic API .apply()
pwm: mtk_disp: fix overflow in period and duty calcalation
pwm: mtk_disp: implement atomic API .get_state()
drivers/pwm/pwm-mtk-disp.c | 172 ++++++++++++++++++++-----------------
1 file changed, 92 insertions(+), 80 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-24 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 8:18 Jitao Shi [this message]
2021-07-24 8:18 ` [PATCH v6 1/5] pwm: mtk-disp: adjust the clocks to avoid them mismatch Jitao Shi
2021-07-24 8:18 ` [PATCH v6 2/5] pwm: mtk_disp: fix force reg to working reg Jitao Shi
2021-08-04 17:12 ` Matthias Brugger
2021-07-24 8:18 ` [PATCH v6 3/5] pwm: mtk_disp: implement atomic API .apply() Jitao Shi
2021-07-24 8:18 ` [PATCH v6 4/5] pwm: mtk_disp: fix overflow in period and duty calcalation Jitao Shi
2021-07-24 8:18 ` [PATCH v6 5/5] pwm: mtk_disp: implement atomic API .get_state() Jitao Shi
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=20210724081849.182108-1-jitao.shi@mediatek.com \
--to=jitao.shi@mediatek.com \
--cc=ck.hu@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=huijuan.xie@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=shuijing.li@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=stonea168@163.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yingjoe.chen@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).