From: John Watts <contact@jookia.org>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>,
boris.brezillon@collabora.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux sunXi <linux-sunxi@lists.linux.dev>
Subject: Re: Question regarding Linux-6.3.5 and Sunxi A20 NAND/NFC support
Date: Fri, 18 Aug 2023 14:41:08 +1000 [thread overview]
Message-ID: <ZN72ZMSPBYvStfzy@titan> (raw)
In-Reply-To: <CAGgoGu4R2Y5Yj4zEQyekZK0Vkb+XpWg+mudmW3LNmfq3tCFDjw@mail.gmail.com>
On Thu, Aug 17, 2023 at 10:21:35PM +0100, Fawad Lateef wrote:
> Hi John,
>
> Thanks for your help. I found the reason for my issue. I defined the
> pinctrl information under the "soc" next to "nfc" entry in
> sunxi-a20.dtsi which was messing it up.
>
> I moved them inside the "pio" dtsi block and NAND is detected now.
Congratulations!
> Though almost all blocks are reported as bad-blocks. I am thinking
> that it's happening as I don't have partition information defined in
> DTS. Do you think that this is the reason for bad-blocks reporting?
I don't have much knowledge here but you might want to confirm the
contents of your bad block table is being read and has correct values.
This might help: https://linux-sunxi.org/Mainline_NAND_Howto
> Regards,
>
> Fawad Lateef
John.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2023-09-16 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 23:40 Question regarding Linux-6.3.5 and Sunxi A20 NAND/NFC support Fawad Lateef
[not found] ` <ZNm2ihdTojuPJM2f@debian.me>
2023-08-14 10:16 ` Fawad Lateef
2023-08-15 22:01 ` Fawad Lateef
[not found] ` <ZNwWNopPItNwKCTV@titan>
2023-08-17 21:21 ` Fawad Lateef
2023-08-18 4:41 ` John Watts [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=ZN72ZMSPBYvStfzy@titan \
--to=contact@jookia.org \
--cc=boris.brezillon@collabora.com \
--cc=fawadlateef@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).