From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: David Runge <dave@sleepmap.de>
Cc: "Ahmed S. Darwish" <a.darwish@linutronix.de>,
linux-rt-users@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24]
Date: Fri, 5 Feb 2021 12:26:38 +0100 [thread overview]
Message-ID: <20210205112638.xuduvuefy3auycht@linutronix.de> (raw)
In-Reply-To: <20210201083441.ocucdvdrv37goz2s@linutronix.de>
On 2021-02-01 09:34:41 [+0100], To David Runge wrote:
> + firewire maintainer
>
> On 2021-01-30 12:46:04 [+0100], David Runge wrote:
> > On 2021-01-29 18:04:14 (+0100), Sebastian Andrzej Siewior wrote:
> > > I don't see anything wrong. There is small difference in timing and
> > > then the RT version does not do a thing while !RT keeps reseting…
> > > Could you try non-RT with the
> > > threadirqs
> > >
> > > option?
> >
> > Yes, (sorry for not including that earlier D:) that fails the same way
> > as the realtime kernel:
> > https://pkgbuild.com/~dvzrv/bugs/2021/01/linux-5.4.91-kernel_threadirqs.log
>
> Could be specific to the chip or the ohci driver. Either way, the problem
> are the threaded interrupts.
David, could you please try a v5.10 kernel with threadirqs? I've been
just told that it works there on a ppc64 box.
> > Best,
> >
> > David
Sebastian
next prev parent reply other threads:[~2021-02-05 11:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 11:59 firewire-ohci fails to initialize Texas Instruments XIO2213A/B/XIO2221 based controller on realtime kernels [5.4.91-rt50, 5.10.8-rt24] David Runge
2021-01-28 6:28 ` Ahmed S. Darwish
2021-01-28 21:41 ` David Runge
2021-01-29 17:04 ` Sebastian Andrzej Siewior
2021-01-30 11:46 ` David Runge
2021-02-01 8:34 ` Sebastian Andrzej Siewior
2021-02-05 11:26 ` Sebastian Andrzej Siewior [this message]
2021-02-05 23:22 ` David Runge
2021-02-07 9:58 ` David Runge
2021-02-08 9:19 ` Sebastian Andrzej Siewior
2021-02-14 19:16 ` David Runge
2021-02-18 8:38 ` Sebastian Andrzej Siewior
2021-02-18 9:27 ` Sebastian Andrzej Siewior
2021-03-08 14:12 ` Sebastian Andrzej Siewior
2021-03-10 18:15 ` David Runge
2021-09-07 23:17 ` David Runge
2021-09-08 2:17 ` Takashi Sakamoto
2021-09-08 17:30 ` David Runge
2021-09-09 0:46 ` Takashi Sakamoto
2021-09-12 18:44 ` David Runge
2021-09-10 11:55 ` Sebastian Andrzej Siewior
2021-09-11 9:46 ` Takashi Sakamoto
2021-09-12 18:53 ` David Runge
2022-01-05 21:01 ` Holger Dehnhardt
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=20210205112638.xuduvuefy3auycht@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=a.darwish@linutronix.de \
--cc=dave@sleepmap.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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).