Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Hans Zhang <hans.zhang@cixtech.com>,
	Heiko Stuebner <heiko@sntech.de>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-rockchip@lists.infradead.org,
	Niklas Cassel <cassel@kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/2] PCI: dw-rockchip: Add L1sub support
Date: Wed, 22 Oct 2025 11:03:15 -0500	[thread overview]
Message-ID: <20251022160315.GA1254908@bhelgaas> (raw)
In-Reply-To: <ffe10dbd-1297-45af-86d5-42023820f2c7@rock-chips.com>

On Wed, Oct 22, 2025 at 08:22:39PM +0800, Shawn Lin wrote:
> 在 2025/10/22 星期三 19:52, Hans Zhang 写道:
> > On 10/22/2025 7:35 PM, Shawn Lin wrote:
> > > The driver should set app_clk_req_n(clkreq ready) of
> > > PCIE_CLIENT_POWER reg
> > > to support L1sub. Otherwise, unset app_clk_req_n and pull down CLKREQ#.

> > > @@ -412,6 +446,8 @@ static int rockchip_pcie_resource_get(struct
> > > platform_device *pdev,
> > >                  return dev_err_probe(&pdev->dev, PTR_ERR(rockchip->rst),
> > >                                       "failed to get reset lines\n");
> > > 
> > > +       rockchip->supports_clkreq = of_property_read_bool(pdev-
> > > >dev.of_node, "supports-clkreq");
> > 
> > This line exceeds 80 characters. Can it be like this?
> 
> Thanks for the reivew.
> 
> I think we've been drop this rule[1] for quite a long time :)
> 
> [1]https://www.phoronix.com/news/Linux-Kernel-Deprecates-80-Col
> 
> > rockchip->supports_clkreq = of_property_read_bool(pdev->dev.of_node,
> >                            "supports-clkreq");

Yes, but that doesn't mean it's OK for the file to be a mishmash where
most of it fits in 80 but random lines go to 100.  That just makes it
a pain to read.

If going past 80 makes something significantly easier to read, that's
fine, and this file does that occasionally for #defines and the like.
But in this case, wrapping to fit in 80 really doesn't hurt anything.

Bjorn

  reply	other threads:[~2025-10-22 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 11:35 [PATCH v2 1/2] PCI: dw-rockchip: Add L1sub support Shawn Lin
2025-10-22 11:35 ` [PATCH v2 2/2] arm64: dts: rockchip: Add PCIe clkreq stuff for RK3588 EVB1 Shawn Lin
2025-10-22 11:52   ` Hans Zhang
2025-10-22 11:52 ` [PATCH v2 1/2] PCI: dw-rockchip: Add L1sub support Hans Zhang
2025-10-22 12:22   ` Shawn Lin
2025-10-22 16:03     ` Bjorn Helgaas [this message]
2025-10-22 13:04 ` Manivannan Sadhasivam
2025-10-22 14:27   ` Shawn Lin
2025-10-22 16:03     ` Manivannan Sadhasivam
2025-10-23  0:39       ` Shawn Lin

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=20251022160315.GA1254908@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=hans.zhang@cixtech.com \
    --cc=heiko@sntech.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=shawn.lin@rock-chips.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