From: Stephen Warren <swarren@wwwdotorg.org>
To: Vidya Sagar <vidyas@nvidia.com>,
thierry.reding@gmail.com, bhelgaas@google.com
Cc: kthota@nvidia.com, linux-tegra@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] PCI: tegra: Enable root port specific features
Date: Tue, 07 Oct 2014 08:44:05 -0700 [thread overview]
Message-ID: <54340A45.4050005@wwwdotorg.org> (raw)
In-Reply-To: <1412677678-12011-1-git-send-email-vidyas@nvidia.com>
On 10/07/2014 03:27 AM, Vidya Sagar wrote:
> Enables root port to advertise its ASPM-L1 capability
> resulting in possible link entry to L1 when an ASPM-L1 capable
> device is connected
> Enables per-controller & per-TMS clock clamping by default
> Enabling above features result in more power saving
>
> It also avoids PM message truncation by waiting for DLLP to finish
> before entering into L1 or L2
>
> Also, it adds helper functions to access root port registers
> diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c
> @@ -1870,8 +1920,10 @@ static int tegra_pcie_enable(struct tegra_pcie *pcie)
>
> tegra_pcie_port_enable(port);
>
> - if (tegra_pcie_port_check_link(port))
> + if (tegra_pcie_port_check_link(port)) {
> + tegra_pcie_enable_rp_features(port);
> continue;
> + }
>
> dev_info(pcie->dev, "link %u down, ignoring\n", port->index);
Wouldn't it be better to have the error case inside the if block; most
error-handling is that way. For example:
if (!tegra_pcie_port_check_link(port)) {
dev_info(pcie->dev, "link %u down, ignoring\n", port->index);
tegra_pcie_port_disable(port);
tegra_pcie_port_free(port);
continue;
}
tegra_pcie_enable_rp_features(port);
... any other "good case" code (of which there admittedly is none at
present)
next prev parent reply other threads:[~2014-10-07 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 10:27 [PATCH v1] PCI: tegra: Enable root port specific features Vidya Sagar
2014-10-07 15:44 ` Stephen Warren [this message]
2014-10-08 7:45 ` Thierry Reding
2014-10-08 7:44 ` Thierry Reding
2014-10-08 7:47 ` Thierry Reding
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=54340A45.4050005@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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