From: Drew Fustini <dfustini@baylibre.com>
To: Suman Anna <s-anna@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tero Kristo <kristo@kernel.org>,
khilman@baylibre.com
Subject: Re: [PATCH] clocksource/drivers/timer-ti-dm: fix regression from errata i940 fix
Date: Wed, 2 Feb 2022 13:36:34 -0800 [thread overview]
Message-ID: <Yfr5YufU9W8Zx/iP@x1> (raw)
In-Reply-To: <69b94cab-43fb-23a7-5819-66a37205bd23@ti.com>
On Wed, Feb 02, 2022 at 03:33:45PM -0600, Suman Anna wrote:
> On 2/2/22 15:25, Drew Fustini wrote:
> > The existing fix for errata i940 causes a conflict for IPU2 which is
> > using timer 3 and 4. From arch/arm/boot/dts/dra7-ipu-dsp-common.dtsi:
> >
> > &ipu2 {
> > mboxes = <&mailbox6 &mbox_ipu2_ipc3x>;
> > ti,timers = <&timer3>;
> > ti,watchdog-timers = <&timer4>, <&timer9>;
> > };
> >
> > I discovered the timer conflict from when booting mainline on a
> > BeagleBoard X15 (AM5728):
> >
> > remoteproc remoteproc1: 55020000.ipu is available
> > remoteproc remoteproc1: powering up 55020000.ipu
> > remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4
> > omap-rproc 55020000.ipu: could not get timer platform device
> > omap-rproc 55020000.ipu: omap_rproc_enable_timers failed: -19
> > remoteproc remoteproc1: can't start rproc 55020000.ipu: -19
> >
> > I modified the errata fix to use timer 15 and 16 instead which resolves
> > the timer conflict.
> >
> > Fixes: 25de4ce5ed02 ("clocksource/drivers/timer-ti-dm: Handle dra7 timer wrap errata i940")
> > Link: https://lore.kernel.org/linux-omap/YfWsG0p6to3IJuvE@x1/
>
> Suggested-by: Suman Anna <s-anna@ti.com>
Yes, thank you for adding.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-02 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 21:25 [PATCH] clocksource/drivers/timer-ti-dm: fix regression from errata i940 fix Drew Fustini
2022-02-02 21:33 ` Suman Anna
2022-02-02 21:36 ` Drew Fustini [this message]
2022-02-03 6:53 ` Tony Lindgren
2022-02-03 15:56 ` Suman Anna
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=Yfr5YufU9W8Zx/iP@x1 \
--to=dfustini@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=j-keerthy@ti.com \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-anna@ti.com \
--cc=tony@atomide.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).