public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Walle <mwalle@kernel.org>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
Cc: linux-mtd@lists.infradead.org, tudor.ambarus@linaro.org,
	vigneshr@ti.com, pratyush@kernel.org, miquel.raynal@bootlin.com,
	richard@nod.at, Hui Wang <hui.wang@canonical.com>
Subject: Re: [PATCH] mtd: spi-nor: infineon: add Cypress (Ramtron) CY15B102QN F-RAM support
Date: Wed, 25 Sep 2024 21:19:09 +0200	[thread overview]
Message-ID: <28ab8b72afee1af59b628f7389f0d7f5@kernel.org> (raw)
In-Reply-To: <36adf15058a6c0ccf5d3842460d3505b282f340e.camel@siemens.com>

Hi,

>> > Similar sad story as with "cy15x104q" where JEDEC ID comes last-byte-first.
>> 
>> Please have a look at
>> https://lore.kernel.org/linux-mtd/20240729102016.8527-2-alessandro.zini@siemens.com/
>> 
>> TLDR, please have a look at at25.c.
> 
> It unfortunately doesn't work with SPI host drivers which only 
> implement spi-mem API.
> Or did I miss something? Otherwise "cy15x104q" could also be handled by 
> at25.c.

The solution here is to add spi-mem support to the at25 driver :) Maybe 
you
can work together wit Hui Wang [1].

-michael

[1] 
https://lore.kernel.org/linux-mtd/20240408124328.777375-1-hui.wang@canonical.com/

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

  reply	other threads:[~2024-09-25 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 16:53 [PATCH] mtd: spi-nor: infineon: add Cypress (Ramtron) CY15B102QN F-RAM support A. Sverdlin
2024-09-24  8:23 ` Michael Walle
2024-09-24 12:31   ` Sverdlin, Alexander
2024-09-25 19:19     ` Michael Walle [this message]
2024-09-26  8:24       ` Sverdlin, Alexander

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=28ab8b72afee1af59b628f7389f0d7f5@kernel.org \
    --to=mwalle@kernel.org \
    --cc=alexander.sverdlin@siemens.com \
    --cc=hui.wang@canonical.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox