linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Eugeniu Rosca <erosca@de.adit-jv.com>,
	Ulrich Hecht <uli+renesas@fpond.eu>,
	"horms@verge.net.au" <horms@verge.net.au>,
	"khiem.nguyen.xt@renesas.com" <khiem.nguyen.xt@renesas.com>,
	"dien.pham.ry@renesas.com" <dien.pham.ry@renesas.com>,
	"takeshi.kihara.df@renesas.com" <takeshi.kihara.df@renesas.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"Wischer, Timo (ADITG/ESM)" <twischer@de.adit-jv.com>,
	"Maik.Scholz@de.bosch.com" <Maik.Scholz@de.bosch.com>,
	"Dirk.Behme@de.bosch.com" <Dirk.Behme@de.bosch.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/5] arm64: dts: r8a7795: Add cpuidle support for CA53 cores
Date: Mon, 29 Jul 2019 12:32:44 +0100	[thread overview]
Message-ID: <20190729113244.GA12631@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAMuHMdXiOBxUDXLcL6R7jHF4DMoH=72yMkSiv-51aV7cw3my9Q@mail.gmail.com>

On Mon, Jul 29, 2019 at 09:44:52AM +0200, Geert Uytterhoeven wrote:
> Hi Eugniu,
> 
> CC cpuidle people
> 
> On Fri, Jul 26, 2019 at 11:47 AM Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
> > On Fri, Jul 26, 2019 at 11:13:29AM +0200, Rosca, Eugeniu (ADITG/ESM1) wrote:
> > [..]
> > > The culprit BSP commits are:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?id=3c3b44c752c4ee
> > > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?id=902ff7caa32dc71c
> > >
> > > Further narrowing it down, it turns out the CA57 cpuidle support is
> > > not responsible for generating the issue. It's all about the CA53 idle
> > > enablement. The reference target is H3-ES2.0-Salvator-X (the problem
> > > originally emerged on M3-based customer HW).
> > [..]
> >
> > Small amendment to the above (based on vanilla testing):
> >
> >  Version                              Issue reproduced?
> >                                       (H3-ES2.0-Salvator-X)
> >  v5.3-rc1-96-g6789f873ed37              No
> >  v5.3-rc1-96-g6789f873ed37 + [1]        No
> >  v5.3-rc1-96-g6789f873ed37 + [2]        No
> >  v5.3-rc1-96-g6789f873ed37 + [1] + [2]  Yes
> >
> > [1] https://patchwork.kernel.org/patch/10769701/
> > ("[v2,1/5] arm64: dts: r8a7795: Add cpuidle support for CA57 cores")
> >
> > [2] https://patchwork.kernel.org/patch/10769689/
> > ("[v2,2/5] arm64: dts: r8a7795: Add cpuidle support for CA53 cores")
> 
> Thanks for your report and investigation!
> 
> Unfortunately your original report didn't make it to lore.kernel.org, and
> probably also not to the list, due to the large audio attachment.
> 
> For the newly CCed people, the issue is about consistent dropouts
> during audio playback using an in-house application, introduced by
> adding cpuidle support to _both_ the big and LITTLE cores.

CPUidle entry/exit latencies are certainly bringing the issue
about, I am not an audio expert but I suspect buffering should
be tuned to cope with those _increased_ latencies or possibly
idle states disabled for certain specific use cases - there
is no silver bullet, entering deep idle states will increase
latencies, there is no way around it.

I am happy to help you debug the issue further.

Lorenzo

  reply	other threads:[~2019-07-29 11:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 10:47 [PATCH v2 0/5] H3/M3-W cpuidle support Ulrich Hecht
2019-01-18 10:47 ` [PATCH v2 1/5] arm64: dts: r8a7795: Add cpuidle support for CA57 cores Ulrich Hecht
2019-08-28 11:47   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 2/5] arm64: dts: r8a7795: Add cpuidle support for CA53 cores Ulrich Hecht
     [not found]   ` <20190726091325.GA13111@vmlxhi-102.adit-jv.com>
2019-07-26  9:47     ` Eugeniu Rosca
2019-07-29  7:44       ` Geert Uytterhoeven
2019-07-29 11:32         ` Lorenzo Pieralisi [this message]
2019-07-29 21:55           ` Eugeniu Rosca
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 3/5] arm64: dts: r8a7796: Add cpuidle support for CA57 cores Ulrich Hecht
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 4/5] arm64: dts: r8a7796: Add cpuidle support for CA53 cores Ulrich Hecht
2019-08-28 11:48   ` Geert Uytterhoeven
2019-01-18 10:47 ` [PATCH v2 5/5] arm64: dts: r8a7796-m3ulcb: Disable " Ulrich Hecht
2019-08-28 12:04 ` [PATCH v2 0/5] H3/M3-W cpuidle support Geert Uytterhoeven
2019-09-03 12:10   ` Geert Uytterhoeven

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=20190729113244.GA12631@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=Dirk.Behme@de.bosch.com \
    --cc=Maik.Scholz@de.bosch.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dien.pham.ry@renesas.com \
    --cc=erosca@de.adit-jv.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=khiem.nguyen.xt@renesas.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=roscaeugeniu@gmail.com \
    --cc=takeshi.kihara.df@renesas.com \
    --cc=twischer@de.adit-jv.com \
    --cc=uli+renesas@fpond.eu \
    /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).