From: Kousik Sanagavarapu <five231003@gmail.com>
To: Nishanth Menon <nm@ti.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kousik Sanagavarapu <five231003@gmail.com>
Subject: [PATCH v4 0/4] Do device node auto cleanup in drivers/soc/ti/
Date: Sun, 25 Aug 2024 14:18:41 +0530 [thread overview]
Message-ID: <20240825085714.10736-1-five231003@gmail.com> (raw)
Do "struct device_node" auto cleanup in soc/ti/. This patch series takes
care of all the cases where this is possible.
Thanks Nishanth for the review on the previous round.
v3:
https://lore.kernel.org/linux-arm-kernel/20240707055341.3656-1-five231003@gmail.com/
Changes since v3:
- s/seperate/separate in the commit msgs througout.
- 1 / 4 - "return ret" instead of "goto rpm_put" as pm_runtime was never
enabled by the time we call pruss_of_setup_memories() in case we
return on err.
v2:
https://lore.kernel.org/linux-arm-kernel/20240703065710.13786-1-five231003@gmail.com/
Changes since v2:
- Split v2 1/3 into v3 1/4 and v3 2/4. The memory setup code is
seperated out of the pruss_probe() function and put into 1/4 and the
actual conversion to auto cleanup is done in 2/4.
- Replace dev_err() with dev_err_probe() in the code paths touched.
v1:
https://lore.kernel.org/linux-arm-kernel/20240510071432.62913-1-five231003@gmail.com/
Changes since v1:
- Refactor code so that it the scope of the pointers touched is reduced,
making the code look more clean.
- The above also the side-effect of fixing the errors that clang emitted
(but my local version of gcc didn't) for PATCH 2/3 during v1.
Kousik Sanagavarapu (4):
soc: ti: pruss: factor out memories setup
soc: ti: pruss: do device_node auto cleanup
soc: ti: knav_qmss_queue: do device_node auto cleanup
soc: ti: pm33xx: do device_node auto cleanup
drivers/soc/ti/knav_qmss_queue.c | 100 +++++++++---------
drivers/soc/ti/pm33xx.c | 52 ++++-----
drivers/soc/ti/pruss.c | 176 ++++++++++++++-----------------
3 files changed, 155 insertions(+), 173 deletions(-)
--
2.46.0.290.g4f02c709e8.dirty
next reply other threads:[~2024-08-25 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 8:48 Kousik Sanagavarapu [this message]
2024-08-25 8:48 ` [PATCH v4 1/4] soc: ti: pruss: factor out memories setup Kousik Sanagavarapu
2024-08-25 8:48 ` [PATCH v4 2/4] soc: ti: pruss: do device_node auto cleanup Kousik Sanagavarapu
2024-08-25 8:48 ` [PATCH v4 3/4] soc: ti: knav_qmss_queue: " Kousik Sanagavarapu
2024-08-25 8:48 ` [PATCH v4 4/4] soc: ti: pm33xx: " Kousik Sanagavarapu
2024-08-28 18:41 ` [PATCH v4 0/4] Do device node auto cleanup in drivers/soc/ti/ Nishanth Menon
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=20240825085714.10736-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nm@ti.com \
--cc=skhan@linuxfoundation.org \
--cc=ssantosh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.