All of lore.kernel.org
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: fix debug prints relevant to PCI devices
Date: Tue, 23 Sep 2014 17:04:08 +0200	[thread overview]
Message-ID: <20140923150407.GJ5982@ulmo> (raw)
In-Reply-To: <20140923140635.GR5182@n2100.arm.linux.org.uk>

On Tue, Sep 23, 2014 at 03:06:35PM +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 23, 2014 at 07:56:01AM -0600, Bjorn Helgaas wrote:
> > This doesn't require any coordination with the PCI core, so I was just
> > leaving this up to the arch.  But I guess I can at least give you my
> > opinion :)
> 
> However, PCI core people have more knowledge of the issues here than I do.
> 
> > > diff --git a/arch/arm/kernel/bios32.c b/arch/arm/kernel/bios32.c
> > > index 17a26c1..03c56ba 100644
> > > --- a/arch/arm/kernel/bios32.c
> > > +++ b/arch/arm/kernel/bios32.c
> > > @@ -290,6 +290,7 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >  {
> > >         struct pci_dev *dev;
> > >         u16 features = PCI_COMMAND_SERR | PCI_COMMAND_PARITY | PCI_COMMAND_FAST_BACK;
> > > +       bool has_pcie_dev = false;
> > >
> > >         /*
> > >          * Walk the devices on this bus, working out what we can
> > > @@ -298,6 +299,8 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >         list_for_each_entry(dev, &bus->devices, bus_list) {
> > >                 u16 status;
> > >
> > > +               if (!has_pcie_dev)
> > > +                       has_pcie_dev = pci_is_pcie(dev);
> > >                 pci_read_config_word(dev, PCI_STATUS, &status);
> > >
> > >                 /*
> > > @@ -354,9 +357,11 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >
> > >         /*
> > >          * Report what we did for this bus
> > > +        * (only if the bus doesn't have any PCIe devices)
> > >          */
> > > -       printk(KERN_INFO "PCI: bus%d: Fast back to back transfers %sabled\n",
> > > -               bus->number, (features & PCI_COMMAND_FAST_BACK) ? "en" : "dis");
> > > +       if (!has_pcie_dev)
> > > +               pr_info("PCI: bus%d: Fast back to back transfers %sabled\n",
> > > +                       bus->number, (features & PCI_COMMAND_FAST_BACK) ? "en" : "dis");
> > 
> > My first choice would be to just drop the printk altogether.
> 
> It can be useful information.
> 
> > If we want to keep the printk, it should be enough to test "bus->self
> > && !pci_is_pcie(bus->self)" to see whether Fast Back-to-Back can be
> > enabled.
> 
> This is exactly the kind of issue that needs to be picked up by core
> PCI people.

I agree. Wouldn't it be more useful to move this into the core?
Disabling fast back-to-back transfers hardly seems like an ARM-
specific "fixup" to me.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140923/14971e59/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Vidya Sagar <sagar.tv@gmail.com>,
	Yijing Wang <wangyijing@huawei.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Will Deacon <will.deacon@arm.com>,
	Stephen Warren <swarren@nvidia.com>,
	Krishna Thota <kthota@nvidia.com>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] ARM: fix debug prints relevant to PCI devices
Date: Tue, 23 Sep 2014 17:04:08 +0200	[thread overview]
Message-ID: <20140923150407.GJ5982@ulmo> (raw)
In-Reply-To: <20140923140635.GR5182@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]

On Tue, Sep 23, 2014 at 03:06:35PM +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 23, 2014 at 07:56:01AM -0600, Bjorn Helgaas wrote:
> > This doesn't require any coordination with the PCI core, so I was just
> > leaving this up to the arch.  But I guess I can at least give you my
> > opinion :)
> 
> However, PCI core people have more knowledge of the issues here than I do.
> 
> > > diff --git a/arch/arm/kernel/bios32.c b/arch/arm/kernel/bios32.c
> > > index 17a26c1..03c56ba 100644
> > > --- a/arch/arm/kernel/bios32.c
> > > +++ b/arch/arm/kernel/bios32.c
> > > @@ -290,6 +290,7 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >  {
> > >         struct pci_dev *dev;
> > >         u16 features = PCI_COMMAND_SERR | PCI_COMMAND_PARITY | PCI_COMMAND_FAST_BACK;
> > > +       bool has_pcie_dev = false;
> > >
> > >         /*
> > >          * Walk the devices on this bus, working out what we can
> > > @@ -298,6 +299,8 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >         list_for_each_entry(dev, &bus->devices, bus_list) {
> > >                 u16 status;
> > >
> > > +               if (!has_pcie_dev)
> > > +                       has_pcie_dev = pci_is_pcie(dev);
> > >                 pci_read_config_word(dev, PCI_STATUS, &status);
> > >
> > >                 /*
> > > @@ -354,9 +357,11 @@ void pcibios_fixup_bus(struct pci_bus *bus)
> > >
> > >         /*
> > >          * Report what we did for this bus
> > > +        * (only if the bus doesn't have any PCIe devices)
> > >          */
> > > -       printk(KERN_INFO "PCI: bus%d: Fast back to back transfers %sabled\n",
> > > -               bus->number, (features & PCI_COMMAND_FAST_BACK) ? "en" : "dis");
> > > +       if (!has_pcie_dev)
> > > +               pr_info("PCI: bus%d: Fast back to back transfers %sabled\n",
> > > +                       bus->number, (features & PCI_COMMAND_FAST_BACK) ? "en" : "dis");
> > 
> > My first choice would be to just drop the printk altogether.
> 
> It can be useful information.
> 
> > If we want to keep the printk, it should be enough to test "bus->self
> > && !pci_is_pcie(bus->self)" to see whether Fast Back-to-Back can be
> > enabled.
> 
> This is exactly the kind of issue that needs to be picked up by core
> PCI people.

I agree. Wouldn't it be more useful to move this into the core?
Disabling fast back-to-back transfers hardly seems like an ARM-
specific "fixup" to me.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-23 15:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07 10:28 [PATCH v4] ARM: fix debug prints relevant to PCI devices Vidya Sagar
2014-09-07 10:28 ` Vidya Sagar
2014-09-11 19:46 ` vidya sagar
2014-09-11 19:46   ` vidya sagar
2014-09-23 13:56 ` Bjorn Helgaas
2014-09-23 13:56   ` Bjorn Helgaas
2014-09-23 14:06   ` Russell King - ARM Linux
2014-09-23 14:06     ` Russell King - ARM Linux
2014-09-23 15:04     ` Thierry Reding [this message]
2014-09-23 15:04       ` Thierry Reding
2014-09-23 15:56       ` Bjorn Helgaas
2014-09-23 15:56         ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2014-06-22 12:44 Vidya Sagar
2014-06-22 12:44 ` Vidya Sagar
2014-06-19  6:36 Vidya Sagar
2014-06-19  6:36 ` Vidya Sagar

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=20140923150407.GJ5982@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.