From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: matthias.bgg@gmail.com
Cc: roger.lu@mediatek.com, khilman@baylibre.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
nfraprado@collabora.com, kernel@collabora.com
Subject: Re: [PATCH 0/6] soc: mediatek: Cleanups for MediaTek SVS driver
Date: Tue, 26 Jul 2022 16:22:06 +0200 [thread overview]
Message-ID: <c9441276-34ae-19dc-8a19-5e03dc14628e@collabora.com> (raw)
In-Reply-To: <20220726141653.177948-1-angelogioacchino.delregno@collabora.com>
Il 26/07/22 16:16, AngeloGioacchino Del Regno ha scritto:
> This is a cleanup-only series for the mtk-svs driver, enhancing the
> usage of standard Linux macros for bitfields for better readability
> and register set/get safety, switches to devm_ functions variants
> where possible and other general cleanups, getting this driver in a
> better overall shape.
>
Sorry, I forgot to write in the cover letter that this series depends
on [1] adding MT8195 and MT8186 support.
[1]: https://patchwork.kernel.org/project/linux-mediatek/list/?series=660955
Regards,
Angelo
> AngeloGioacchino Del Regno (6):
> soc: mediatek: mtk-svs: Commonize t-calibration-data fuse array read
> soc: mediatek: mtk-svs: Switch to platform_get_irq()
> soc: mediatek: mtk-svs: Remove hardcoded irqflags
> soc: mediatek: mtk-svs: Drop of_match_ptr() for of_match_table
> soc: mediatek: mtk-svs: Use devm variant for dev_pm_opp_of_add_table()
> soc: mediatek: mtk-svs: Use bitfield access macros where possible
>
> drivers/soc/mediatek/mtk-svs.c | 325 ++++++++++++++++++---------------
> 1 file changed, 176 insertions(+), 149 deletions(-)
>
prev parent reply other threads:[~2022-07-26 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 14:16 [PATCH 0/6] soc: mediatek: Cleanups for MediaTek SVS driver AngeloGioacchino Del Regno
2022-07-26 14:16 ` [PATCH 1/6] soc: mediatek: mtk-svs: Commonize t-calibration-data fuse array read AngeloGioacchino Del Regno
2022-08-25 13:27 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 2/6] soc: mediatek: mtk-svs: Switch to platform_get_irq() AngeloGioacchino Del Regno
2022-08-25 13:26 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 3/6] soc: mediatek: mtk-svs: Remove hardcoded irqflags AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 4/6] soc: mediatek: mtk-svs: Drop of_match_ptr() for of_match_table AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 5/6] soc: mediatek: mtk-svs: Use devm variant for dev_pm_opp_of_add_table() AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 6/6] soc: mediatek: mtk-svs: Use bitfield access macros where possible AngeloGioacchino Del Regno
2022-08-25 13:29 ` Matthias Brugger
2022-08-25 18:50 ` Nícolas F. R. A. Prado
2022-08-29 9:36 ` AngeloGioacchino Del Regno
2022-08-29 9:33 ` AngeloGioacchino Del Regno
2022-08-29 11:02 ` Matthias Brugger
2022-07-26 14:22 ` AngeloGioacchino Del Regno [this message]
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=c9441276-34ae-19dc-8a19-5e03dc14628e@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=roger.lu@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