From: Hao Chang <ot_chhao.chang@mediatek.com>
To: Sean Wang <seann.wang@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Wenbin Mei <wenbin.mei@mediatek.com>,
Axe Yang <axe.yang@mediatek.com>,
Qingliang Li <qingliang.li@mediatek.com>,
Hanks Chen <hanks.chen@mediatek.com>,
Chunhui Li <chunhui.li@mediatek.com>,
<linux-mediatek@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"Hao Chang" <ot_chhao.chang@mediatek.com>
Subject: [RESEND v3 0/2]
Date: Sat, 25 Jan 2025 10:51:21 +0800 [thread overview]
Message-ID: <20250125025145.14405-1-ot_chhao.chang@mediatek.com> (raw)
Change in v3:
1)Add error handling to prevent memory leaks 2)Move the eint pin assignment action to eint for processing
---
This patch depends on
[v3,2/2] pinctrl: mediatek: add mt8196 driver [v3,1/2] dt-bindings: pinctrl: mediatek: add support for mt8196
Please also accept this patch together with [1] to avoid build and dt binding check error.
[1]https://patchwork.kernel.org/project/linux-mediatek/list/?series=&submitter=215008&state=&q=v3&archive=&delegate=
---
Hao Chang (2):
pinctrl: mediatek: update EINT base retrieval method
pinctrl: mediatek: adapt to multi-base design
drivers/pinctrl/mediatek/mtk-eint.c | 38 +++++++++-----
.../pinctrl/mediatek/pinctrl-mtk-common-v2.c | 50 +++++++++++++------
2 files changed, 60 insertions(+), 28 deletions(-)
--
2.46.0
next reply other threads:[~2025-01-25 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 2:51 Hao Chang [this message]
2025-01-25 2:51 ` [RESEND v3 1/2] pinctrl: mediatek: update EINT base retrieval method Hao Chang
2025-01-25 2:51 ` [RESEND v3 2/2] pinctrl: mediatek: adapt to multi-base design Hao Chang
2025-01-27 11:48 ` AngeloGioacchino Del Regno
2025-02-19 7:28 ` Chhao Chang (常浩)
2025-02-19 7:53 ` Chen-Yu Tsai
2025-02-19 8:02 ` Chhao Chang (常浩)
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=20250125025145.14405-1-ot_chhao.chang@mediatek.com \
--to=ot_chhao.chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axe.yang@mediatek.com \
--cc=chunhui.li@mediatek.com \
--cc=hanks.chen@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qingliang.li@mediatek.com \
--cc=seann.wang@kernel.org \
--cc=wenbin.mei@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