From: Hans Zhang <18255117159@163.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
lpieralisi@kernel.org
Cc: manivannan.sadhasivam@linaro.org, thierry.reding@gmail.com,
kw@linux.com, robh@kernel.org, bhelgaas@google.com,
jonathanh@nvidia.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [v3] PCI: tegra194: Fix debugfs directory creation when CONFIG_PCIEASPM is disabled
Date: Sun, 27 Apr 2025 09:19:52 +0800 [thread overview]
Message-ID: <d9da0347-ce8c-4b5e-91d9-d85ea6fa41d7@163.com> (raw)
In-Reply-To: <580c1b6a-ba32-48ea-9fd8-59884d0dbcbf@wanadoo.fr>
On 2025/4/8 03:43, Christophe JAILLET wrote:
> Hi,
>
> Nitpick: PATCH is missing within the [] in the subject.
>
>
> Le 07/04/2025 à 14:43, Hans Zhang a écrit :
>> Previously, the debugfs directory was unconditionally created in
>> tegra_pcie_config_rp() regardless of the CONFIG_PCIEASPM setting.
>> This led to unnecessary directory creation when ASPM support was
>> disabled.
>>
>> Move the debugfs directory creation into init_debugfs() which is
>> conditionally compiled based on CONFIG_PCIEASPM. This ensures:
>> - The directory is only created when ASPM-related debugfs entries are
>> needed.
>> - Proper error handling for directory creation failures.
>> - Avoids cluttering debugfs with empty directories when ASPM is disabled.
>>
>> Signed-off-by: Hans Zhang <18255117159@163.com>
>> ---
>> Changes since v2:
>> https://lore.kernel.org/linux-pci/20250406134355.49036-1-18255117159@163.com/
>>
>> - Maintainer recommends ignoring the devm_kasprintf return value. The
>> module should still work correctly. So just a return;
>
> Note, that I'm not a maintainer ;-)
>
> For what it worth:
>
> Reviewed-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
>
> CJ
>>
>> Changes since v1:
>> https://lore.kernel.org/linux-pci/20250405145459.26800-1-18255117159@163.com/
>>
>> - The first version was committed incorrectly because the judgment
>> parameter in "debugfs_remove_recursive" was not noticed.
>> ---
>> drivers/pci/controller/dwc/pcie-tegra194.c | 19 ++++++++++---------
>> 1 file changed, 10 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c
>> b/drivers/pci/controller/dwc/pcie-tegra194.c
>> index 5103995cd6c7..bc419688527a 100644
>> --- a/drivers/pci/controller/dwc/pcie-tegra194.c
>> +++ b/drivers/pci/controller/dwc/pcie-tegra194.c
>> @@ -713,7 +713,16 @@ static void init_host_aspm(struct tegra_pcie_dw
>> *pcie)
>> static void init_debugfs(struct tegra_pcie_dw *pcie)
>> {
>> - debugfs_create_devm_seqfile(pcie->dev, "aspm_state_cnt",
>> pcie->debugfs,
>> + struct device *dev = pcie->dev;
>> + char *name;
>> +
>> + name = devm_kasprintf(dev, GFP_KERNEL, "%pOFP", dev->of_node);
>> + if (!name)
>> + return;
>> +
>> + pcie->debugfs = debugfs_create_dir(name, NULL);
>> +
>> + debugfs_create_devm_seqfile(dev, "aspm_state_cnt", pcie->debugfs,
>> aspm_state_cnt);
>> }
>> #else
>> @@ -1634,7 +1643,6 @@ static void tegra_pcie_deinit_controller(struct
>> tegra_pcie_dw *pcie)
>> static int tegra_pcie_config_rp(struct tegra_pcie_dw *pcie)
>> {
>> struct device *dev = pcie->dev;
>> - char *name;
>> int ret;
>> pm_runtime_enable(dev);
>> @@ -1664,13 +1672,6 @@ static int tegra_pcie_config_rp(struct
>> tegra_pcie_dw *pcie)
>> goto fail_host_init;
>> }
>> - name = devm_kasprintf(dev, GFP_KERNEL, "%pOFP", dev->of_node);
>> - if (!name) {
>> - ret = -ENOMEM;
>> - goto fail_host_init;
>> - }
>> -
>> - pcie->debugfs = debugfs_create_dir(name, NULL);
>> init_debugfs(pcie);
>> return ret;
>>
>> base-commit: a8662bcd2ff152bfbc751cab20f33053d74d0963
Dear all,
I see that the status of this patch is Rejected and I want to know why.
Best regards,
Hans
next prev parent reply other threads:[~2025-04-27 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 12:43 [v3] PCI: tegra194: Fix debugfs directory creation when CONFIG_PCIEASPM is disabled Hans Zhang
2025-04-07 19:43 ` Christophe JAILLET
2025-04-08 2:02 ` Hans Zhang
2025-04-27 1:19 ` Hans Zhang [this message]
2025-05-02 17:44 ` Manivannan Sadhasivam
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=d9da0347-ce8c-4b5e-91d9-d85ea6fa41d7@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox