From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Han Xu <han.xu@nxp.com>,
linux-mtd@lists.infradead.org,
Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: FIX Re: GPMI IMX6ull timeout on dma
Date: Wed, 27 Jan 2021 18:01:01 +0100 [thread overview]
Message-ID: <CAOf5uwnSyRF7zTjbsNbJAWu+iabMofthx+gTOL+4wVOPDURJRw@mail.gmail.com> (raw)
In-Reply-To: <20181029105312.1a62628c@xps13>
Hi all
On Mon, Oct 29, 2018 at 10:53 AM Miquel Raynal
<miquel.raynal@bootlin.com> wrote:
>
> Hi Michael,
>
> Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote on
> Mon, 29 Oct 2018 10:43:05 +0100:
>
> > Hi
> >
> > On Mon, Oct 29, 2018 at 10:41 AM Miquel Raynal
> > <miquel.raynal@bootlin.com> wrote:
> > >
> > > Hi Michael,
> > >
> > > Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote on
> > > Fri, 5 Oct 2018 12:32:18 +0200:
> > >
> > > > Hi Boris
> > > >
> > > > I have reverted for now
> > > >
> > > > Revert "mtd: rawnand: gpmi: support ->setup_data_interface()"
> > > > This reverts commit 76e1a0086a0c3276b384f77905345e0fcc886fdd.
> > > >
> > > > Revert "mtd: rawnand: gpmi: use core timings instead of an empirical
> > > > derivation"
> > > > This reverts commit b1206122069aadabe1a8c50789277a978aaa4df7.
> > >
> > > Sorry for the delay, I've been very busy lately.
> > >
> > > Please also Cc: me in your e-mails to the MTD ML.
> > >
> > > AFAIR I'm the author of these patches so I would like to understand and
> > > fix what's wrong there. As a start, can you discriminate which patch
> > > actually makes the timings inconsistent? Are you ready to do more
> > > testing to find what's wrong?
> >
> > Yes it's on my plan. Now for field I need to revert them but I have
> > them in roadmap.
> > We are testing now an imx6dl. It can be a combination with the micron
> > part number too.
>
> Sure, let us know about your discoveries, I really want the GPMI driver
> to use core timings and ->setup_data_interface() so if there is
> something wrong there it should be fixed.
>
Need to move on lts kernel and I have time to work and I must work on
this topic. I don't see any update but
another report. Is this supposed to be fixed?
Michael
> Thanks,
> Miquèl
--
Michael Nazzareno Trimarchi
Amarula Solutions BV
COO Co-Founder
Cruquiuskade 47 Amsterdam 1018 AM NL
T. +31(0)851119172
M. +39(0)3479132170
[`as] https://www.amarulasolutions.com
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-01-27 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 13:22 GPMI IMX6ull timeout on dma Michael Nazzareno Trimarchi
2018-10-04 14:36 ` Michael Nazzareno Trimarchi
2018-10-05 10:32 ` FIX " Michael Nazzareno Trimarchi
2018-10-29 9:40 ` Miquel Raynal
2018-10-29 9:43 ` Michael Nazzareno Trimarchi
2018-10-29 9:53 ` Miquel Raynal
2021-01-27 17:01 ` Michael Nazzareno Trimarchi [this message]
2021-01-27 19:12 ` Miquel Raynal
2021-01-27 19:43 ` Michael Nazzareno Trimarchi
2021-01-27 19:50 ` Miquel Raynal
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=CAOf5uwnSyRF7zTjbsNbJAWu+iabMofthx+gTOL+4wVOPDURJRw@mail.gmail.com \
--to=michael@amarulasolutions.com \
--cc=boris.brezillon@bootlin.com \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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).