From: Fawad Lateef <fawadlateef@gmail.com>
To: John Watts <contact@jookia.org>
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: Thu, 17 Aug 2023 22:21:35 +0100 [thread overview]
Message-ID: <CAGgoGu4R2Y5Yj4zEQyekZK0Vkb+XpWg+mudmW3LNmfq3tCFDjw@mail.gmail.com> (raw)
In-Reply-To: <ZNwWNopPItNwKCTV@titan>
On Wed, 16 Aug 2023 at 01:20, John Watts <contact@jookia.org> wrote:
>
> On Tue, Aug 15, 2023 at 11:01:02PM +0100, Fawad Lateef wrote:
> > Hi everyone,
> >
> > Can someone guide me? I am not sure what I am missing here.
> >
> > I am trying to debug the code but I assume that the SUNXI NAND driver
> > is supposed to be working and that something is missing from my
> > changes and additions to the dts/dtsi for A20 SOM.
> >
> > Thanks in advance
>
> Hi there Fawad,
>
> I've hit this problem before and it's usually been because the pins are being
> used by another peripheral already
>
> Could you post the kernel log? It might have some notes on this.
>
> John.
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.
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?
Regards,
Fawad Lateef
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-08-17 21:23 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 [this message]
2023-08-18 4:41 ` John Watts
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=CAGgoGu4R2Y5Yj4zEQyekZK0Vkb+XpWg+mudmW3LNmfq3tCFDjw@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=contact@jookia.org \
--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 NNTP newsgroup(s).