From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: aaro.koskinen@iki.fi
Cc: Mathieu Malaterre <malat@debian.org>,
Linux-MIPS <linux-mips@linux-mips.org>,
linux-mmc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Ezequiel Garcia <ezequiel@collabora.co.uk>
Subject: Re: Bug report: MIPS CI20/jz4740-mmc DMA and PREEMPT_NONE
Date: Mon, 12 Nov 2018 18:04:06 -0300 [thread overview]
Message-ID: <CAAEAJfBUEj+4RnHmK9RvOv7cghQNr0xNqr5GdVTG+V88+Kzi8Q@mail.gmail.com> (raw)
In-Reply-To: <20181017195050.GA20347@darkstar.musicnaut.iki.fi>
On Wed, 17 Oct 2018 at 16:50, Aaro Koskinen <aaro.koskinen@iki.fi> wrote:
>
> Hi,
>
> On Wed, Oct 17, 2018 at 03:38:07PM +0200, Mathieu Malaterre wrote:
> > Since CONFIG_PREEMPT has been 'y' since at least commit 0752f92934292
> > could you confirm that the original mmc driver (kernel from imgtech
> > people) did work ok with PREEMPT_NONE (sorry I did not do my homework)
> > ?
>
> Sorry, cannot confirm or test that. I have only used the mainline kernel
> on this board, since v4.5 or so with my own custom config which has
> been PREEMPT_NONE until now.
>
Aaro,
I spent some time today investigating this issue. I think this driver
has a broken pre-request/post-request implementation.
Will post some patches soon.
Thanks for the report,
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2018-11-12 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 17:04 Bug report: MIPS CI20/jz4740-mmc DMA and PREEMPT_NONE Aaro Koskinen
2018-10-17 13:38 ` Mathieu Malaterre
2018-10-17 19:50 ` Aaro Koskinen
2018-11-12 21:04 ` Ezequiel Garcia [this message]
2018-10-17 17:55 ` Ezequiel Garcia
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=CAAEAJfBUEj+4RnHmK9RvOv7cghQNr0xNqr5GdVTG+V88+Kzi8Q@mail.gmail.com \
--to=ezequiel@vanguardiasur.com.ar \
--cc=aaro.koskinen@iki.fi \
--cc=ezequiel@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=malat@debian.org \
--cc=ulf.hansson@linaro.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).