mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Mihai Sain <mihai.sain@microchip.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: microchip: sama7g54_curiosity: Add fixed-partitions for spi-nor flash
Date: Mon, 12 May 2025 18:24:17 +0300	[thread overview]
Message-ID: <c1f42c52-0cbd-4673-90cf-3e1c4de38e92@tuxon.dev> (raw)
In-Reply-To: <20250429064547.5807-1-mihai.sain@microchip.com>



On 29.04.2025 09:45, Mihai Sain wrote:
> Add fixed-partitions for spi-nor flash to match the at91 boot flow
> and layout of the nand flash.
> Partitions can be listed from /proc/mtd:
> 
> [root@sama7g54 ~]$ cat /proc/mtd | grep qspi
> mtd6: 00040000 00001000 "qspi1: at91bootstrap"
> mtd7: 00100000 00001000 "qspi1: u-boot"
> mtd8: 00040000 00001000 "qspi1: u-boot env"
> mtd9: 00080000 00001000 "qspi1: device tree"
> mtd10: 00600000 00001000 "qspi1: kernel"
> 
> [root@sama7g54 ~]$ mtdinfo /dev/mtd10
> mtd10
> Name:                           qspi1: kernel
> Type:                           nor
> Eraseblock size:                4096 bytes, 4.0 KiB
> Amount of eraseblocks:          1536 (6291456 bytes, 6.0 MiB)
> Minimum input/output unit size: 1 byte
> Sub-page size:                  1 byte
> Character device major/minor:   90:20
> Bad blocks are allowed:         false
> Device is writable:             true
> 
> Signed-off-by: Mihai Sain <mihai.sain@microchip.com>

Applied to at91-dt, thanks!

      reply	other threads:[~2025-05-12 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29  6:45 Mihai Sain
2025-05-12 15:24 ` Claudiu Beznea [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=c1f42c52-0cbd-4673-90cf-3e1c4de38e92@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.sain@microchip.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®