From: Bjorn Helgaas <helgaas@kernel.org>
To: Yicong Yang <yangyicong@hisilicon.com>
Cc: linux-pci@vger.kernel.org, f.fangjian@huawei.com
Subject: Re: [Patch] PCI:add 32 GT/s decoding in some macros
Date: Mon, 13 Jan 2020 15:17:28 -0600 [thread overview]
Message-ID: <20200113211728.GA113776@google.com> (raw)
In-Reply-To: <1578883220-28222-1-git-send-email-yangyicong@hisilicon.com>
On Mon, Jan 13, 2020 at 10:40:20AM +0800, Yicong Yang wrote:
> Link speed 32.0 GT/s is supported in PCIe r5.0. Add in macro
> PCIE_SPEED2STR and PCIE_SPEED2MBS_ENC to correctly decode.
> This patch is a complementary to
> commit de76cda215d5 ("PCI: Decode PCIe 32 GT/s link speed")
Thanks for the patch! Can you please rework current_link_speed_show()
(which was updated by de76cda215d5 ("PCI: Decode PCIe 32 GT/s link
speed")) so we don't duplicate the strings there and in
PCIE_SPEED2STR()?
Maybe something like:
switch (linkstat & PCI_EXP_LNKSTA_CLS) {
case PCI_EXP_LNKSTA_CLS_32_0GB:
speed = PCIE_SPEED2STR(PCIE_SPEED_32_0GT);
break;
...
My goal is to both remove the string duplication and make it more
likely that when we add the *next* new speed, we'll catch everything
the first time around.
Bjorn
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> ---
> drivers/pci/pci.h | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
> index 3f6947e..2cd64bd 100644
> --- a/drivers/pci/pci.h
> +++ b/drivers/pci/pci.h
> @@ -288,7 +288,8 @@ void pci_bus_put(struct pci_bus *bus);
>
> /* PCIe link information */
> #define PCIE_SPEED2STR(speed) \
> - ((speed) == PCIE_SPEED_16_0GT ? "16 GT/s" : \
> + ((speed) == PCIE_SPEED_32_0GT ? "32 GT/s" : \
> + (speed) == PCIE_SPEED_16_0GT ? "16 GT/s" : \
> (speed) == PCIE_SPEED_8_0GT ? "8 GT/s" : \
> (speed) == PCIE_SPEED_5_0GT ? "5 GT/s" : \
> (speed) == PCIE_SPEED_2_5GT ? "2.5 GT/s" : \
> @@ -296,7 +297,8 @@ void pci_bus_put(struct pci_bus *bus);
>
> /* PCIe speed to Mb/s reduced by encoding overhead */
> #define PCIE_SPEED2MBS_ENC(speed) \
> - ((speed) == PCIE_SPEED_16_0GT ? 16000*128/130 : \
> + ((speed) == PCIE_SPEED_32_0GT ? 32000*128/130 : \
> + (speed) == PCIE_SPEED_16_0GT ? 16000*128/130 : \
> (speed) == PCIE_SPEED_8_0GT ? 8000*128/130 : \
> (speed) == PCIE_SPEED_5_0GT ? 5000*8/10 : \
> (speed) == PCIE_SPEED_2_5GT ? 2500*8/10 : \
> --
> 2.8.1
>
next prev parent reply other threads:[~2020-01-13 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 2:40 [Patch] PCI:add 32 GT/s decoding in some macros Yicong Yang
2020-01-13 21:17 ` Bjorn Helgaas [this message]
2020-01-14 1:17 ` Yicong Yang
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=20200113211728.GA113776@google.com \
--to=helgaas@kernel.org \
--cc=f.fangjian@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=yangyicong@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.