linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI: tegra: Implement ->add_bus() callback
Date: Fri, 4 Dec 2015 14:01:10 -0600	[thread overview]
Message-ID: <20151204200110.GF20125@localhost> (raw)
In-Reply-To: <1448282426-2642-2-git-send-email-thierry.reding@gmail.com>

On Mon, Nov 23, 2015 at 01:40:26PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> The configuration space mapping on Tegra is somewhat special, and in

It'd be nice to have a tiny hint about specifically what is special
about Tegra config space mapping.

> order to avoid wasting virtual address space the configuration space
> for each bus needs to be stitched together from several blocks which
> form a single continuous virtual address range for accessors.
> 
> Currently the configuration space is mapped upon the first access to
> one of its registers. However, the mapping operation may sleep under
> certain circumstances, so doing it from the configuration space
> accessors (they are protected by a spin lock) will trigger a warning.

Can you include the exact warning?  Does it happen always?  Always on
the first config access to a bus?

> To avoid the warning, use the ->add_bus() callback to perform the
> mapping at enumeration time when the operation is allowed to sleep.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>  drivers/pci/host/pci-tegra.c | 40 +++++++++++++++++++---------------------
>  1 file changed, 19 insertions(+), 21 deletions(-)
> 
> diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c
> index 3018ae52e092..c3666f9d7ef1 100644
> --- a/drivers/pci/host/pci-tegra.c
> +++ b/drivers/pci/host/pci-tegra.c
> @@ -426,31 +426,23 @@ free:
>  	return ERR_PTR(err);
>  }
>  
> -/*
> - * Look up a virtual address mapping for the specified bus number. If no such
> - * mapping exists, try to create one.
> - */
> -static void __iomem *tegra_pcie_bus_map(struct tegra_pcie *pcie,
> -					unsigned int busnr)
> +static int tegra_pcie_add_bus(struct pci_bus *bus)
>  {
> -	struct tegra_pcie_bus *bus;
> +	struct tegra_pcie *pcie = sys_to_pcie(bus->sysdata);
> +	struct tegra_pcie_bus *b;
>  
> -	list_for_each_entry(bus, &pcie->buses, list)
> -		if (bus->nr == busnr)
> -			return (void __iomem *)bus->area->addr;
> +	b = tegra_pcie_bus_alloc(pcie, bus->number);
> +	if (IS_ERR(b))
> +		return PTR_ERR(b);
>  
> -	bus = tegra_pcie_bus_alloc(pcie, busnr);
> -	if (IS_ERR(bus))
> -		return NULL;
> +	list_add_tail(&b->list, &pcie->buses);
>  
> -	list_add_tail(&bus->list, &pcie->buses);
> -
> -	return (void __iomem *)bus->area->addr;
> +	return 0;
>  }
>  
> -static void __iomem *tegra_pcie_conf_address(struct pci_bus *bus,
> -					     unsigned int devfn,
> -					     int where)
> +static void __iomem *tegra_pcie_map_bus(struct pci_bus *bus,
> +					unsigned int devfn,
> +					int where)
>  {
>  	struct tegra_pcie *pcie = sys_to_pcie(bus->sysdata);
>  	void __iomem *addr = NULL;
> @@ -466,7 +458,12 @@ static void __iomem *tegra_pcie_conf_address(struct pci_bus *bus,
>  			}
>  		}
>  	} else {
> -		addr = tegra_pcie_bus_map(pcie, bus->number);
> +		struct tegra_pcie_bus *b;
> +
> +		list_for_each_entry(b, &pcie->buses, list)
> +			if (b->nr == bus->number)
> +				addr = (void __iomem *)b->area->addr;
> +
>  		if (!addr) {
>  			dev_err(pcie->dev,
>  				"failed to map cfg. space for bus %u\n",
> @@ -481,7 +478,8 @@ static void __iomem *tegra_pcie_conf_address(struct pci_bus *bus,
>  }
>  
>  static struct pci_ops tegra_pcie_ops = {
> -	.map_bus = tegra_pcie_conf_address,
> +	.add_bus = tegra_pcie_add_bus,
> +	.map_bus = tegra_pcie_map_bus,
>  	.read = pci_generic_config_read32,
>  	.write = pci_generic_config_write32,
>  };
> -- 
> 2.5.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-04 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 12:40 [PATCH 1/2] PCI: Add pci_ops.add_bus() callback Thierry Reding
2015-11-23 12:40 ` [PATCH 2/2] PCI: tegra: Implement ->add_bus() callback Thierry Reding
2015-12-04 20:01   ` Bjorn Helgaas [this message]
2015-12-04 19:50 ` [PATCH 1/2] PCI: Add pci_ops.add_bus() callback Bjorn Helgaas

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=20151204200110.GF20125@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=gnurou@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).