From: Anand Moon <linux.amoon@gmail.com>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-omap@vger.kernel.org (open list:PCI DRIVER FOR TI
DRA7XX/J721E),
linux-pci@vger.kernel.org (open list:PCI DRIVER FOR TI
DRA7XX/J721E),
linux-arm-kernel@lists.infradead.org (moderated list:PCI DRIVER
FOR TI DRA7XX/J721E), linux-kernel@vger.kernel.org (open list)
Cc: Anand Moon <linux.amoon@gmail.com>
Subject: [RFC v1 0/2] PCI: j721e: A couple of cleanups
Date: Mon, 13 Oct 2025 15:47:22 +0530 [thread overview]
Message-ID: <20251013101727.129260-1-linux.amoon@gmail.com> (raw)
Refactor the J721e probe function to use devres helpers for resource
management. This replaces manual clock handling with
devm_clk_get_optional_enabled() and assigns the reset GPIO directly
to the struct members, eliminating unnecessary local variables.
These patches have been compile-tested only, as I do not have access
to the hardware for runtime verification.
Thanks
-Anand
Anand Moon (2):
PCI: j721e: Use devm_clk_get_optional_enabled() to get the clock
PCI: j721e: Use inline reset GPIO assignment and drop local variable
drivers/pci/controller/cadence/pci-j721e.c | 25 +++++++---------------
1 file changed, 8 insertions(+), 17 deletions(-)
base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
--
2.50.1
next reply other threads:[~2025-10-13 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:17 Anand Moon [this message]
2025-10-13 10:17 ` [RFC v1 1/2] PCI: j721e: Use devm_clk_get_optional_enabled() to get the clock Anand Moon
2025-10-13 11:13 ` Siddharth Vadapalli
2025-10-13 14:02 ` Anand Moon
2025-10-13 10:17 ` [RFC v1 2/2] PCI: j721e: Use inline reset GPIO assignment and drop local variable Anand Moon
2025-10-13 11:22 ` Siddharth Vadapalli
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=20251013101727.129260-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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).