All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: SSunk <ssunkkan@gmail.com>
Cc: miquel.raynal@bootlin.com, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org, pratyush@kernel.org,
	richard@nod.at, ssunkkan@gmail.com, tudor.ambarus@linaro.org,
	vigneshr@ti.com
Subject: Re: [PATCH] Add support for more XMC series
Date: Thu, 17 Aug 2023 19:10:21 +0200	[thread overview]
Message-ID: <abd705350b650717dbbc187815d384e7@walle.cc> (raw)
In-Reply-To: <20230817170335.3711-1-ssunkkan@gmail.com>

Hi,

>> XMC parts seem to have SFDP tables and they should work out of the box
>> without any patches with the generic spi nor driver [1]. Therefore,
>> you don't need any entry at all.
> 
> I think it is related to the PARSE_SFDP flag.
> The XMC flash part supports SFDP, so i don’t needto add
> NO_SFDP_FLAGS() macro.

Correct. If the flash is working with PARSE_SFDP, it has SFDP and
all the information of the flash_info table is pulled from the SFDP
tables, except for the part name. Therefore, you don't need any entry
at all. The flash should just work out of the box. Are you using the
latest kernel?

-michael

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

  reply	other threads:[~2023-08-17 17:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 12:46 [PATCH] Add support for more XMC series SSunk
2023-08-17 13:14 ` Michael Walle
2023-08-17 13:20 ` Miquel Raynal
2023-08-17 17:03   ` SSunk
2023-08-17 17:10     ` Michael Walle [this message]
2023-08-17 17:17       ` Clus Tom
2023-08-29  4:56         ` SSunk
2023-08-29  6:48           ` Michael Walle
2023-08-31  4:13             ` SSunk
2023-08-31  6:41               ` Michael Walle
     [not found] <20230812030731.3711-1-ssunkkan@gmail.com>
2023-12-06 12:33 ` Jagan Teki
     [not found] <20230812031846.3958-1-ssunkkan@gmail.com>
     [not found] ` <CAPnjgZ1Z6pKEif5HKFLcG0AQJL1qrqy9j78TjvuhpsOUzS7JGQ@mail.gmail.com>
     [not found]   ` <CABjXDjHOpcM=JtCe2SGzwQ+GbQT7cg8xQxFbthPqW3KXaJ1P3Q@mail.gmail.com>
2023-08-14 22:42     ` Simon Glass
2023-08-15  2:46       ` Clus Tom
2023-08-31  4:07         ` SSunk
2023-08-31  5:48         ` SSunk

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=abd705350b650717dbbc187815d384e7@walle.cc \
    --to=michael@walle.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=ssunkkan@gmail.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.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.