devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: bhelgaas@google.com, robh+dt@kernel.org, mark.rutland@arm.com,
	thierry.reding@gmail.com, jonathanh@nvidia.com, kishon@ti.com,
	catalin.marinas@arm.com, will.deacon@arm.com,
	jingoohan1@gmail.com, gustavo.pimentel@synopsys.com,
	digetx@gmail.com, mperttunen@nvidia.com,
	linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kthota@nvidia.com,
	mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V11 03/12] PCI: dwc: Perform dbi regs write lock towards the end
Date: Thu, 27 Jun 2019 16:50:47 +0100	[thread overview]
Message-ID: <20190627155047.GF3782@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <ecae46b4-54cc-7f4d-5a86-908431fd472a@nvidia.com>

On Thu, Jun 27, 2019 at 09:03:08PM +0530, Vidya Sagar wrote:
> On 6/27/2019 8:28 PM, Lorenzo Pieralisi wrote:
> > On Mon, Jun 24, 2019 at 02:44:56PM +0530, Vidya Sagar wrote:
> > > Remove multiple write enable and disable sequences of dbi registers as
> > > Tegra194 implements writes to BAR-0 register (offset: 0x10) controlled by
> > > DBI write-lock enable bit thereby not allowing any further writes to BAR-0
> > > register in config space to take place. Hence enabling write permission at
> > > the start of function and disabling the same only towards the end.
> > 
> > I do not understand what this patch does, I would like to rephrase
> > the commit log in a way that is easier to parse.
> > 
> > In particular I do not get what you mean in relation to BAR-0, I am
> > confused, please clarify.
> > 
> > Lorenzo
> Well, some of the Synopsys DesignWare core's DBI registers are
> protected with a lock without which, they are read-only by default.
> Existing code in dw_pcie_setup_rc() API tries to unlock and lock
> multiple times whenever it wants to update those write-protected
> registers. This patch attempts to unlock all such write-protected
> registers for writing once in the beginning of the function and lock
> them back towards the end.  As far as BAR-0 register (which is at
> offset 0x10 in DBI space... nothing but the config space) in Tegra194
> is concerned, it is one of those registers to which writes are
> protected. I could have added unlock/lock pair around accessing this
> register, but that would bloat this API with one more pair of
> unlock/lock, instead I chose to remove unlock/lock pairs for all
> protected registers and have unlock in the beginning and lock towards
> the end.

Ok, so DBI space registers that require write permissions are per-IP.
This is clearer so the commit log must be rewritten, it is not clear at
all in this respect at least not as-is, if you read it you will
notice ;-)

Lorenzo

> 
> -Vidya Sagar
> 
> > 
> > > Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> > > Reviewed-by: Thierry Reding <treding@nvidia.com>
> > > Acked-by: Jingoo Han <jingoohan1@gmail.com>
> > > ---
> > > Changes since [v10]:
> > > * None
> > > 
> > > Changes since [v9]:
> > > * None
> > > 
> > > Changes since [v8]:
> > > * None
> > > 
> > > Changes since [v7]:
> > > * None
> > > 
> > > Changes since [v6]:
> > > * None
> > > 
> > > Changes since [v5]:
> > > * Moved write enable to the beginning of the API and write disable to the end
> > > 
> > > Changes since [v4]:
> > > * None
> > > 
> > > Changes since [v3]:
> > > * None
> > > 
> > > Changes since [v2]:
> > > * None
> > > 
> > > Changes since [v1]:
> > > * None
> > > 
> > >   drivers/pci/controller/dwc/pcie-designware-host.c | 14 ++++++++------
> > >   1 file changed, 8 insertions(+), 6 deletions(-)
> > > 
> > > diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> > > index f93252d0da5b..d3156446ff27 100644
> > > --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> > > +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> > > @@ -628,6 +628,12 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
> > >   	u32 val, ctrl, num_ctrls;
> > >   	struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
> > > +	/*
> > > +	 * Enable DBI read-only registers for writing/updating configuration.
> > > +	 * Write permission gets disabled towards the end of this function.
> > > +	 */
> > > +	dw_pcie_dbi_ro_wr_en(pci);
> > > +
> > >   	dw_pcie_setup(pci);
> > >   	if (!pp->ops->msi_host_init) {
> > > @@ -650,12 +656,10 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
> > >   	dw_pcie_writel_dbi(pci, PCI_BASE_ADDRESS_1, 0x00000000);
> > >   	/* Setup interrupt pins */
> > > -	dw_pcie_dbi_ro_wr_en(pci);
> > >   	val = dw_pcie_readl_dbi(pci, PCI_INTERRUPT_LINE);
> > >   	val &= 0xffff00ff;
> > >   	val |= 0x00000100;
> > >   	dw_pcie_writel_dbi(pci, PCI_INTERRUPT_LINE, val);
> > > -	dw_pcie_dbi_ro_wr_dis(pci);
> > >   	/* Setup bus numbers */
> > >   	val = dw_pcie_readl_dbi(pci, PCI_PRIMARY_BUS);
> > > @@ -687,15 +691,13 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
> > >   	dw_pcie_wr_own_conf(pp, PCI_BASE_ADDRESS_0, 4, 0);
> > > -	/* Enable write permission for the DBI read-only register */
> > > -	dw_pcie_dbi_ro_wr_en(pci);
> > >   	/* Program correct class for RC */
> > >   	dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI);
> > > -	/* Better disable write permission right after the update */
> > > -	dw_pcie_dbi_ro_wr_dis(pci);
> > >   	dw_pcie_rd_own_conf(pp, PCIE_LINK_WIDTH_SPEED_CONTROL, 4, &val);
> > >   	val |= PORT_LOGIC_SPEED_CHANGE;
> > >   	dw_pcie_wr_own_conf(pp, PCIE_LINK_WIDTH_SPEED_CONTROL, 4, val);
> > > +
> > > +	dw_pcie_dbi_ro_wr_dis(pci);
> > >   }
> > >   EXPORT_SYMBOL_GPL(dw_pcie_setup_rc);
> > > -- 
> > > 2.17.1
> > > 
> 

  reply	other threads:[~2019-06-27 15:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24  9:14 [PATCH V11 00/12] Add Tegra194 PCIe support Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 01/12] PCI: Add #defines for some of PCIe spec r4.0 features Vidya Sagar
2019-06-27 14:38   ` Lorenzo Pieralisi
2019-07-01 12:42     ` Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 02/12] PCI: Disable MSI for Tegra root ports Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 03/12] PCI: dwc: Perform dbi regs write lock towards the end Vidya Sagar
2019-06-27 14:58   ` Lorenzo Pieralisi
2019-06-27 15:33     ` Vidya Sagar
2019-06-27 15:50       ` Lorenzo Pieralisi [this message]
2019-06-27 16:52         ` Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 04/12] PCI: dwc: Move config space capability search API Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 05/12] PCI: dwc: Add ext " Vidya Sagar
2019-06-24  9:14 ` [PATCH V11 06/12] dt-bindings: PCI: designware: Add binding for CDM register check Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 07/12] PCI: dwc: Add support to enable " Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 08/12] dt-bindings: Add PCIe supports-clkreq property Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 09/12] dt-bindings: PCI: tegra: Add device tree support for Tegra194 Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 10/12] dt-bindings: PHY: P2U: Add Tegra194 P2U block Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 11/12] phy: tegra: Add PCIe PIPE2UPHY support Vidya Sagar
2019-06-24  9:15 ` [PATCH V11 12/12] PCI: tegra: Add Tegra194 PCIe support 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=20190627155047.GF3782@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kishon@ti.com \
    --cc=kthota@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mmaddireddy@nvidia.com \
    --cc=mperttunen@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.com \
    --cc=will.deacon@arm.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).