linux-mtd.lists.infradead.org archive mirror
 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 23:54:09 +0200	[thread overview]
Message-ID: <20190729235409.222c8880@jawa> (raw)
In-Reply-To: <CAOMZO5C4UgetHAW6_JqLGZH96_8TyHSzj10DxFe+XMnZR07ASA@mail.gmail.com>


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

Hi Fabio,

> Hi Lukasz,
> 
> On Mon, Jul 29, 2019 at 5:43 PM Lukasz Majewski <lukma@denx.de> wrote:
> 
> > Thank you for your reply, Fabio.  
> 
> I assume you are using arch/arm/boot/dts/vf610-bk4.dts
> 
> In this file I see that you only define the DATA0 and DATA1 pins for
> QSPI0_B:
> 
> VF610_PAD_PTD11__QSPI0_B_DATA1 0x397f
> VF610_PAD_PTD12__QSPI0_B_DATA0 0x397f
> 
> Don't you also need to define DATA2 and DATA3?
> 

You got me  :-) [1]

The DATA2 and DATA3 (for QSPI0_B "lane") are used for other purposes -
this is how the PCB was designed.

At best it is possible to have both memories working with double SPI
configuration or single (QSPI0_A with quad SPI [2]).

(And hence it is why I've asked Andrey for sharing his DTS files).

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


Note:

[1] -
https://elixir.bootlin.com/linux/latest/source/arch/arm/boot/dts/vf610-bk4.dts#L235

[2] -
https://elixir.bootlin.com/linux/latest/source/arch/arm/boot/dts/vf610-bk4.dts#L491



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 21:54 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
2019-07-29 21:17     ` Fabio Estevam
2019-07-29 21:54       ` Lukasz Majewski [this message]
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=20190729235409.222c8880@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 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).