linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-stable <stable@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	lkft-triage@lists.linaro.org,
	Linux Kernel Functional Testing <lkft@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: juno: Enable more SMMUs
Date: Mon, 14 Feb 2022 20:41:51 +0530	[thread overview]
Message-ID: <CA+G9fYsUX2vHjNwZ7u=JtACEyfe9SkSHtYnwJXJ1JytF9+pSAQ@mail.gmail.com> (raw)
In-Reply-To: <20220214141303.3lmnassl4qibsp3y@bogus>

On Mon, 14 Feb 2022 at 19:43, Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> On Mon, Feb 14, 2022 at 07:36:00PM +0530, Naresh Kamboju wrote:
> > Hi Robin,
> >
> > Since we did not get a reply on this email thread.
> > and those intermittent failures are causing a lot of noise in reports summary.
> > We will wait one more week and stop running 64k page size testing on
> > Juno-r2 devices.
> >
> > > > > diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi b/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > > index 8e7a66943b01..d3148730e951 100644
> > > > > --- a/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > > +++ b/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > > @@ -545,8 +545,7 @@ pcie_ctlr: pcie@40000000 {
> > > > >                           <0x02000000 0x00 0x50000000 0x00 0x50000000 0x0 0x08000000>,
> > > > >                           <0x42000000 0x40 0x00000000 0x40 0x00000000 0x1 0x00000000>;
> > > > >                  /* Standard AXI Translation entries as programmed by EDK2 */
> > > > > -               dma-ranges = <0x02000000 0x0 0x2c1c0000 0x0 0x2c1c0000 0x0 0x00040000>,
> > > > > -                            <0x02000000 0x0 0x80000000 0x0 0x80000000 0x0 0x80000000>,
> > > > > +               dma-ranges = <0x02000000 0x0 0x80000000 0x0 0x80000000 0x0 0x80000000>,
> > > > >                               <0x43000000 0x8 0x00000000 0x8 0x00000000 0x2 0x00000000>;
> > > > >                  #interrupt-cells = <1>;
> > > > >                  interrupt-map-mask = <0 0 0 7>;
> > > > >
> >
> > Reference email thread,
> > https://lore.kernel.org/stable/0a1d437d-9ea0-de83-3c19-e07f560ad37c@arm.com/
> >
>
> I was about to tag the fix for this and was just reading this thread. I will
> send the pull request soon. Sorry for the delay, it is in next for some time
> now. Are you seeing the issue even in linux-next ?

Due to load balance / test queue maintenance on Juno-r2 devices,
We have stopped running 64k page testing on mainline and next instead
running on stable-rc builds.

Allow me a day to test Linux next 64k page size build testing on
Juno-r2 and get back to you.

- Naresh

  reply	other threads:[~2022-02-14 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <720d0a9a42e33148fcac45cd39a727093a32bf32.1614965598.git.robin.murphy@arm.com>
2021-03-23  9:30 ` [PATCH 1/2] arm64: dts: juno: Describe PCI dma-ranges Sudeep Holla
     [not found] ` <a730070d718cb119f77c8ca1782a0d4189bfb3e7.1614965598.git.robin.murphy@arm.com>
2021-07-30 12:17   ` [PATCH 2/2] arm64: dts: juno: Enable more SMMUs Robin Murphy
2021-07-30 14:34     ` Anders Roxell
2021-07-30 14:44       ` Robin Murphy
2021-07-30 14:57         ` Anders Roxell
2021-09-14  9:46         ` Anders Roxell
2022-02-14 14:06           ` Naresh Kamboju
2022-02-14 14:13             ` Sudeep Holla
2022-02-14 15:11               ` Naresh Kamboju [this message]
2022-02-16 11:32                 ` Naresh Kamboju
2022-02-16 14:31                   ` Sudeep Holla

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='CA+G9fYsUX2vHjNwZ7u=JtACEyfe9SkSHtYnwJXJ1JytF9+pSAQ@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=Liviu.Dudau@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=robin.murphy@arm.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudeep.holla@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).