linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shradha Todi" <shradha.t@samsung.com>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	"'PCI'" <linux-pci@vger.kernel.org>,
	"'Jingoo Han'" <jingoohan1@gmail.com>,
	"'Gustavo Pimentel'" <gustavo.pimentel@synopsys.com>,
	"'Lorenzo Pieralisi'" <lorenzo.pieralisi@arm.com>,
	"'Bjorn Helgaas'" <bhelgaas@google.com>,
	"'Pankaj Dubey'" <pankaj.dubey@samsung.com>
Subject: RE: [PATCH] PCI: dwc: Add upper limit address for outbound iATU
Date: Thu, 24 Dec 2020 11:06:50 +0530	[thread overview]
Message-ID: <095e01d6d9b6$cad59ac0$6080d040$@samsung.com> (raw)
In-Reply-To: <CAL_JsqKdzu8EgY-pqxH+ZyDh3ALJGccqgPuj=cc==SGbMvYZJw@mail.gmail.com>

> From: Rob Herring <robh@kernel.org>
> Subject: Re: [PATCH] PCI: dwc: Add upper limit address for outbound iATU
> 
> On Sun, Dec 20, 2020 at 6:56 PM Shradha Todi <shradha.t@samsung.com>
> wrote:
> >
> > The size parameter is unsigned long type which can accept size > 4GB.
> > In that case, the upper limit address must be programmed. Add support
> > to program the upper limit address and set INCREASE_REGION_SIZE in
> > case size > 4GB.
> 
> Not all DWC h/w versions have the upper register and bit. Is it safe to write to
> the non-existent register?

Thanks for the review.
Surely it exists post 4.80a version of controller but I am not sure in 
which version of the controller this was introduced. I can figure this
out from the SNPS team and update the patch accordingly.

> 
> >
> > Signed-off-by: Shradha Todi <shradha.t@samsung.com>
> > ---
> >  drivers/pci/controller/dwc/pcie-designware.c | 8 ++++++--
> > drivers/pci/controller/dwc/pcie-designware.h | 1 +
> >  2 files changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/controller/dwc/pcie-designware.c
> > b/drivers/pci/controller/dwc/pcie-designware.c
> > index 28c56a1..7eba3b2 100644
> > --- a/drivers/pci/controller/dwc/pcie-designware.c
> > +++ b/drivers/pci/controller/dwc/pcie-designware.c
> > @@ -290,12 +290,16 @@ static void __dw_pcie_prog_outbound_atu(struct
> dw_pcie *pci, u8 func_no,
> >                            upper_32_bits(cpu_addr));
> >         dw_pcie_writel_dbi(pci, PCIE_ATU_LIMIT,
> >                            lower_32_bits(cpu_addr + size - 1));
> > +       dw_pcie_writel_dbi(pci, PCIE_ATU_UPPER_LIMIT,
> > +                          upper_32_bits(cpu_addr + size - 1));
> 
> If not safe, perhaps only write if non-zero.
> 
Writing zero has no side-affect and we have tested this.

> >         dw_pcie_writel_dbi(pci, PCIE_ATU_LOWER_TARGET,
> >                            lower_32_bits(pci_addr));
> >         dw_pcie_writel_dbi(pci, PCIE_ATU_UPPER_TARGET,
> >                            upper_32_bits(pci_addr));
> > -       dw_pcie_writel_dbi(pci, PCIE_ATU_CR1, type |
> > -                          PCIE_ATU_FUNC_NUM(func_no));
> > +       val = type | PCIE_ATU_FUNC_NUM(func_no);
> > +       val = upper_32_bits(size - 1) ?
> > +               val | PCIE_ATU_INCREASE_REGION_SIZE : val;
> > +       dw_pcie_writel_dbi(pci, PCIE_ATU_CR1, val);
> >         dw_pcie_writel_dbi(pci, PCIE_ATU_CR2, PCIE_ATU_ENABLE);
> >
> >         /*
> > diff --git a/drivers/pci/controller/dwc/pcie-designware.h
> > b/drivers/pci/controller/dwc/pcie-designware.h
> > index b09329b..28b72fb 100644
> > --- a/drivers/pci/controller/dwc/pcie-designware.h
> > +++ b/drivers/pci/controller/dwc/pcie-designware.h
> > @@ -106,6 +106,7 @@
> >  #define PCIE_ATU_DEV(x)                        FIELD_PREP(GENMASK(23, 19), x)
> >  #define PCIE_ATU_FUNC(x)               FIELD_PREP(GENMASK(18, 16), x)
> >  #define PCIE_ATU_UPPER_TARGET          0x91C
> > +#define PCIE_ATU_UPPER_LIMIT           0x924
> >
> >  #define PCIE_MISC_CONTROL_1_OFF                0x8BC
> >  #define PCIE_DBI_RO_WR_EN              BIT(0)
> > --
> > 2.7.4
> >


      reply	other threads:[~2020-12-24  5:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20201218153043epcas5p1831d9bc440e9e05609792f19dfeb4012@epcas5p1.samsung.com>
2020-12-18 15:30 ` [PATCH] PCI: dwc: Add upper limit address for outbound iATU Shradha Todi
2020-12-21 16:06   ` Rob Herring
2020-12-24  5:36     ` Shradha Todi [this message]

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='095e01d6d9b6$cad59ac0$6080d040$@samsung.com' \
    --to=shradha.t@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=robh@kernel.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 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).