From: "Krzysztof Wilczyński" <kw@linux.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu, git@xilinx.com,
bharat.kumar.gogada@xilinx.com, Hyun Kwon <hyun.kwon@xilinx.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Marc Zyngier <maz@kernel.org>,
Ravi Kiran Gummaluri <rgummal@xilinx.com>,
Rob Herring <robh@kernel.org>, Sasha Levin <sashal@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: xilinx-nwl: Enable the clock through CCF
Date: Wed, 23 Jun 2021 15:53:26 +0200 [thread overview]
Message-ID: <20210623135326.GA54420@rocinante> (raw)
In-Reply-To: <be603822953d0a815034a952b9c71bac642f22ae.1624454607.git.michal.simek@xilinx.com>
[+cc Sasha for visibility]
Hi Michal,
Thank you for sending v2 so promptly! And for all the extra changes and
fixes. Much appreciated!
> Enable PCIE reference clock. There is no remove function that's why
> this should be enough for simple operation.
> Normally this clock is enabled by default by firmware but there are
> usecases where this clock should be enabled by driver itself.
> It is also good that clock user is recorded in clock framework.
Small nitpicks: it would be PCIe here in the above and in the error
message (this is as per [1]), and "use cases" also in the above.
This can be corrected when the patch will be merged by either Bjorn or
Lorenzo, to avoid sending v3 unnecessarily, provided that they would
have a moment to do it, of course.
> Fixes: ab597d35ef11 ("PCI: xilinx-nwl: Add support for Xilinx NWL PCIe Host Controller")
Thank you!
Does it make sense for this change to be back-ported to stable and
long-term kernels?
I am asking to make sure we do the right thing here, as I can imagine
that older kernels (primarily because some folks could use, for example,
Ubuntu LTS releases for development) might often be used by people who
work with the Xilinx FPGAs and such.
[...]
> + err = clk_prepare_enable(pcie->clk);
> + if (err) {
> + dev_err(dev, "can't enable pcie ref clock\n");
> + return err;
> + }
> +
As per the nitpick above, it would be "PCIe", but probably no need to
send v3 to correct this.
1. https://lore.kernel.org/linux-pci/20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com/
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-23 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:23 [PATCH v2 0/2] PCI: xilinx-nwl: Add clock handling Michal Simek
2021-06-23 13:23 ` [PATCH v2 1/2] dt-bindings: pci: xilinx-nwl: Document optional clock property Michal Simek
2021-06-23 13:23 ` [PATCH v2 2/2] PCI: xilinx-nwl: Enable the clock through CCF Michal Simek
2021-06-23 13:53 ` Krzysztof Wilczyński [this message]
2021-06-23 14:00 ` Michal Simek
2021-06-23 14:19 ` Krzysztof Wilczyński
2021-06-25 10:48 ` Michal Simek
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=20210623135326.GA54420@rocinante \
--to=kw@linux.com \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=git@xilinx.com \
--cc=hyun.kwon@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rgummal@xilinx.com \
--cc=robh@kernel.org \
--cc=sashal@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