From: Shawn Lin <shawn.lin@rock-chips.com>
To: Anand Moon <linux.amoon@gmail.com>
Cc: shawn.lin@rock-chips.com,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"open list:PCIE DRIVER FOR ROCKCHIP" <linux-pci@vger.kernel.org>,
"open list:PCIE DRIVER FOR ROCKCHIP"
<linux-rockchip@lists.infradead.org>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v1 0/5] Fix some register offset as per RK3399 TRM part 2
Date: Tue, 18 Nov 2025 08:54:26 +0800 [thread overview]
Message-ID: <20d86c90-9066-4a44-8fff-f4e3edef256e@rock-chips.com> (raw)
In-Reply-To: <20251117181023.482138-1-linux.amoon@gmail.com>
Hi Anand,
在 2025/11/18 星期二 2:10, Anand Moon 写道:
> In order to enable ASPM we need to fix the register offset as
> RK3399 TRM part 2 - PCIe Controller.
>
> Tested on Radxa Rock Pi 4b.
>
I checked your patch, and it looks like indeed we made some mistakes
here. Could you add fixes tag for each?
BTW, regarding to patch 1, I think you should leave out ASPM part, that
should be another topic after these fixes.
> Thanks
> -Anand
>
> Anand Moon (5):
> PCI: rockchip: Fix Link Control register offset and enable ASPM/CLKREQ
> PCI: rockchip: Fix Device Control register offset for Max payload size
> PCI: rockchip: Fix Slot Capability Register offset for slot power
> limit
> PCI: rockchip: Fix Link Control and Status Register 2 for target link
> speed
> PCI: rockchip: Fix Linkwidth Control Register offset for Retrain Link
>
> drivers/pci/controller/pcie-rockchip-host.c | 31 +++++++++++----------
> drivers/pci/controller/pcie-rockchip.h | 5 ++++
> 2 files changed, 21 insertions(+), 15 deletions(-)
>
>
> base-commit: e7c375b181600caf135cfd03eadbc45eb530f2cb
prev parent reply other threads:[~2025-11-18 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 18:10 [RFC v1 0/5] Fix some register offset as per RK3399 TRM part 2 Anand Moon
2025-11-17 18:10 ` [RFC v1 1/5] PCI: rockchip: Fix Link Control register offset and enable ASPM/CLKREQ Anand Moon
2025-11-18 17:50 ` Bjorn Helgaas
2025-11-19 14:19 ` Anand Moon
2025-11-20 3:44 ` Bjorn Helgaas
2025-11-20 13:58 ` Anand Moon
2025-11-26 10:33 ` Anand Moon
2025-11-26 14:39 ` Bjorn Helgaas
2025-11-27 7:34 ` Anand Moon
2025-11-17 18:10 ` [RFC v1 2/5] PCI: rockchip: Fix Device Control register offset for Max payload size Anand Moon
2025-11-18 0:50 ` Bjorn Helgaas
2025-11-18 11:16 ` Anand Moon
2025-11-17 18:10 ` [RFC v1 3/5] PCI: rockchip: Fix Slot Capability Register offset for slot power limit Anand Moon
2025-11-17 18:10 ` [RFC v1 4/5] PCI: rockchip: Fix Link Control and Status Register 2 for target link speed Anand Moon
2025-11-17 18:10 ` [RFC v1 5/5] PCI: rockchip: Fix Linkwidth Control Register offset for Retrain Link Anand Moon
2025-11-18 0:54 ` Shawn Lin [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=20d86c90-9066-4a44-8fff-f4e3edef256e@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=bhelgaas@google.com \
--cc=heiko@sntech.de \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox