All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>,
	Boris Brezillon <bbrezillon@kernel.org>,
	Andrey Smirnov <andrew.smirnov@gmail.com>,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	linux-mtd@lists.infradead.org, NXP Linux Team <linux-imx@nxp.com>,
	Suresh Gupta <suresh.gupta@nxp.com>,
	Chris Healy <cphealy@gmail.com>
Subject: Re: [imx][vybrid][qspi] Regression notification - vybrid vf610 QUADSPI - BK4 board
Date: Mon, 29 Jul 2019 22:43:26 +0200	[thread overview]
Message-ID: <20190729224326.44aa3057@jawa> (raw)
In-Reply-To: <CAOMZO5CsTPaRSe-VmOwnnYrsMMXa3GhurmsWwzaPo948xs10FA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2254 bytes --]

Hi Fabio,

> Hi Lukasz,
> 
> On Wed, Jul 24, 2019 at 7:11 PM Lukasz Majewski <lukma@denx.de> wrote:
> >
> > Dear All,
> >
> > I'd like to report that after moving the fsl-quadspi.c driver
> > from ./drivers/mtd to ./drivers/spi (around 5.1-rc1) [1] the
> > Vybrid's QUADSPI (even with single SPI-NOR memory connected) is not
> > working anymore (the chip ID read is FF FF FF).
> >
> > This wouldn't be a problem per-se, but not all necessary code was
> > moved
> > - especially for vybrid which has issues with some HW bugs [2]:
> >  
> > --------------->8----------------  
> >  * The IC guy suggests we use the "AHB Command Read" which is faster
> >  * then the "IP Command Read". (What's more is that there is a bug
> > in
> >  * the "IP Command Read" in the Vybrid.)
> > ---------------8<----------------
> >
> > I've explicitly asked NXP support for this HW issue [3] - but till
> > now there was no reply.
> >
> > The official linux-imx (from meta-freescale) seems not to support
> > vybrid (vf610) anymore - and the newest available now kernel is
> > 4.19 (with the old fsl-quadspi.c driver available).
> >
> >
> >
> > Hence the question - has anybody noticed this issue and (maybe) is
> > working on it?  
> 
> I don't have access to a Vybrid board, but I kindly got the
> confirmation from Andrey on Cc that QSPI is working fine on his Vybrid
> based board running linux-next.
> 

Thank you for your reply, Fabio.

Andrey , could you share your setup info? How your memories are
connected?

Would it be possible to share your dts files for linux-next?

I did a bit more debugging and the old driver (before conversion) on my
setup breaks when I try to erase/write/read 256+ bytes (with dd's block
size -> bs = 1).

Could you check if erase, write and read of

dd if=/dev/urandom of=/dev/mtd7 bs=1 count=256 

works as expected?


Writing larger chunks (with bs=64) works as expected.

> Regards,
> 
> Fabio Estevam




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 144 bytes --]

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-07-29 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 22:11 [imx][vybrid][qspi] Regression notification - vybrid vf610 QUADSPI - BK4 board Lukasz Majewski
2019-07-29 19:09 ` Fabio Estevam
2019-07-29 20:43   ` Lukasz Majewski [this message]
2019-07-29 21:17     ` Fabio Estevam
2019-07-29 21:54       ` Lukasz Majewski
2019-07-30  3:48         ` Fabio Estevam
2019-07-30 15:14           ` Lukasz Majewski
2019-07-30  3:07     ` Andrey Smirnov

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=20190729224326.44aa3057@jawa \
    --to=lukma@denx.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=bbrezillon@kernel.org \
    --cc=cphealy@gmail.com \
    --cc=festevam@gmail.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=suresh.gupta@nxp.com \
    --cc=yogeshnarayan.gaur@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.