From: "Cédric Le Goater" <clg@kaod.org>
To: Shakeeb B K <shakeebbk@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: [ast2500] aspeed-smc fail with MX25L25635F
Date: Tue, 6 Apr 2021 10:51:16 +0200 [thread overview]
Message-ID: <5747c839-afc1-68e3-b792-d40d29e9fcdb@kaod.org> (raw)
In-Reply-To: <CABYu0Wj5nCs1hkGGd4860otC53fdzRECq4_+TbesgaW6zOZC2Q@mail.gmail.com>
On 4/5/21 8:08 AM, Shakeeb B K wrote:
> Hi Cédric,
>
> On Fri, Apr 2, 2021 at 12:45 PM Cédric Le Goater <clg@kaod.org <mailto:clg@kaod.org>> wrote:
>
> Hello,
>
> On 4/1/21 5:22 PM, Shakeeb B K wrote:
> > Hi Cédric,
> >
> > The part we are using is *MX25L25635F* https://www.macronix.com/Lists/Datasheet/Attachments/7414/MX25L25635F,%203V,%20256Mb,%20v1.5.pdf <https://www.macronix.com/Lists/Datasheet/Attachments/7414/MX25L25635F,%203V,%20256Mb,%20v1.5.pdf> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.macronix.com%2FLists%2FDatasheet%2FAttachments%2F7414%2FMX25L25635F%2C%25203V%2C%2520256Mb%2C%2520v1.5.pdf&data=04%7C01%7Cspasha%40nvidia.com%7C4cf89d8779c84d638c6f08d8ef7d0919%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637522667609971209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hYy5Cpi06y4T0DpFb4%2FDeo2nEy5Cn3rf3l%2BEO%2FaPP%2FU%3D&reserved=0
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.macronix.com%2FLists%2FDatasheet%2FAttachments%2F7414%2FMX25L25635F%2C%25203V%2C%2520256Mb%2C%2520v1.5.pdf&data=04%7C01%7Cspasha%40nvidia.com%7C4cf89d8779c84d638c6f08d8ef7d0919%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637522667609971209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hYy5Cpi06y4T0DpFb4%2FDeo2nEy5Cn3rf3l%2BEO%2FaPP%2FU%3D&reserved=0>>
> >
> > Attaching the failed boot log - full_boot.log
>
> This was failing in 5.8 already.
>
>
> > The patch that fixes the problem - workaround.patch
>
> OK. You are disabling Dual I/O.
>
> > A patch to override read opcode - 001-Debug.patch
> > Failing log with post fixup read opcode update - fail_post_fixup.log
>
> Could you check the SPI wiring on the schematics of your AST2500 dgx board ?
>
> If it is single wired, then I suggest a work around like the one attached.
>
>
> We have MOSI, MISO datalines connected and the workaround is working for us.
> But I just wanted to check if anybody got dual mode working with MX25L25635F,
IBM has at least two systems using dual data reads on the MX25L25635F
with the ast2400 and the ast2500 SoC.
> and what would be the right fix for it in spi-nor.
a DT property would be the best solution.
C.
prev parent reply other threads:[~2021-04-06 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 16:02 [ast2500] aspeed-smc fail with MX25L25635F Shakeeb B K
2021-04-01 10:17 ` Shakeeb B K
2021-04-01 11:22 ` Cédric Le Goater
2021-04-01 15:22 ` Shakeeb B K
2021-04-02 7:15 ` Cédric Le Goater
2021-04-05 6:08 ` Shakeeb B K
2021-04-06 8:51 ` Cédric Le Goater [this message]
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=5747c839-afc1-68e3-b792-d40d29e9fcdb@kaod.org \
--to=clg@kaod.org \
--cc=openbmc@lists.ozlabs.org \
--cc=shakeebbk@gmail.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).