From: Anand Moon <linux.amoon@gmail.com>
To: "Thierry Reding" <thierry.reding@gmail.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>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org (open list:PCI DRIVER FOR NVIDIA
TEGRA),
linux-pci@vger.kernel.org (open list:PCI DRIVER FOR NVIDIA TEGRA),
linux-kernel@vger.kernel.org (open list)
Cc: Anand Moon <linux.amoon@gmail.com>
Subject: [RFC v1 0/2] PCI: tegra: A couple of cleanups
Date: Mon, 1 Sep 2025 00:30:49 +0530 [thread overview]
Message-ID: <20250831190055.7952-1-linux.amoon@gmail.com> (raw)
Hi All,
This small series provides two cleanup patches for the Tegra PCIe driver.
The overall goal is to replace custom, open-coded logic with standard
kernel helper functions.
These changes improve the driver's readability and maintainability by
everaging modern, well-tested APIs for clock management and register
polling.
Thanks
-Anand
Anand Moon (2):
PCI: tegra: Simplify clock handling by using clk_bulk*() functions
PCI: tegra: Use readl_poll_timeout() for link status polling
drivers/pci/controller/pci-tegra.c | 109 +++++++----------------------
1 file changed, 27 insertions(+), 82 deletions(-)
base-commit: 5c3b3264e5858813632031ba58bcd6e1eeb3b214
--
2.50.1
next reply other threads:[~2025-08-31 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 19:00 Anand Moon [this message]
2025-08-31 19:00 ` [RFC v1 1/2] PCI: tegra: Simplify clock handling by using clk_bulk*() functions Anand Moon
2025-09-17 13:44 ` Jon Hunter
2025-09-17 18:26 ` Anand Moon
2025-09-18 9:17 ` Jon Hunter
2025-09-18 15:06 ` Anand Moon
2025-09-18 16:46 ` Jon Hunter
2025-08-31 19:00 ` [RFC v1 2/2] PCI: tegra: Use readl_poll_timeout() for link status polling Anand Moon
2025-09-17 3:14 ` Mikko Perttunen
2025-09-17 7:45 ` Anand Moon
2025-09-18 1:25 ` Mikko Perttunen
2025-09-18 4:20 ` Anand Moon
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=20250831190055.7952-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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 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.