U-boot Archive mirror
 help / color / mirror / Atom feed
From: Alexey Romanov <avromanov@salutedevices.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: "dario.binacchi@amarulasolutions.com"
	<dario.binacchi@amarulasolutions.com>,
	"frieder.schrempf@kontron.de" <frieder.schrempf@kontron.de>,
	"kmpark@infradead.org" <kmpark@infradead.org>,
	 "hs@denx.de" <hs@denx.de>,
	"joe.hershberger@ni.com" <joe.hershberger@ni.com>,
	 "dunaev@tecon.ru" <dunaev@tecon.ru>,
	"sjg@chromium.org" <sjg@chromium.org>,
	"bmeng@tinylab.org" <bmeng@tinylab.org>,
	"xypron.glpk@gmx.de" <xypron.glpk@gmx.de>,
	"tobias@waldekranz.com" <tobias@waldekranz.com>,
	"jpewhacker@gmail.com" <jpewhacker@gmail.com>,
	"marek.vasut+renesas@mailbox.org"
	<marek.vasut+renesas@mailbox.org>,
	"kever.yang@rock-chips.com" <kever.yang@rock-chips.com>,
	"jbx6244@gmail.com" <jbx6244@gmail.com>,
	"abdellatif.elkhlifi@arm.com" <abdellatif.elkhlifi@arm.com>,
	"mikhail.kshevetskiy@iopsys.eu" <mikhail.kshevetskiy@iopsys.eu>,
	"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
	kernel <kernel@sberdevices.ru>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH v3 0/3] Introduce mtdblock device
Date: Mon, 6 May 2024 13:56:17 +0000	[thread overview]
Message-ID: <20240506135607.aprjqn7uyng2jgp5@cab-wsm-0029881> (raw)
In-Reply-To: <CAOf5uwkGoHVzDvvz3pqCsro2VC+Vxj-YaKKkye=n=AU8w8dJmA@mail.gmail.com>

Hello Michael,

On Thu, Apr 11, 2024 at 06:14:29PM +0200, Michael Nazzareno Trimarchi wrote:
> Hi
> 
> I will review tomorrow, I need have a time window to test even on my board

Any news?

> 
> Mihcael
> 
> On Thu, Apr 11, 2024 at 6:09 PM Alexey Romanov
> <avromanov@salutedevices.com> wrote:
> >
> > Hello! Ping.
> >
> > On Thu, Apr 04, 2024 at 01:58:10PM +0300, Alexey Romanov wrote:
> > > Hello!
> > >
> > > This series adds support for the mtdblock device, which
> > > allows to read/write data block by block. For example,
> > > it can now be used for BCB or Android AB command:
> > >
> > >   $ bcb load mtd 0 part_name
> > >
> > > Tested only on SPI NAND, so bind is made only for
> > > SPI NAND drivers.
> > >
> > > ---
> > >
> > > Changes V1 -> V2 [1]:
> > >
> > >   - Drop patch [2].
> > >   - Add warning if bind NAND mtdblock device.
> > >   - Move documentation of mtdblock implementation
> > >     from commit message to the source code.
> > >   - Remove __maybe_unused from mtd partition functions
> > >     description.
> > >   - Use blk_enabled() instead of #ifdefs.
> > >
> > > Changes V2 -> V3 [2]:
> > >
> > >   - Rebased over [3].
> > >   - Rename mtd_bread/bwrite -> mtd_blk_read/write.
> > >   - Fix GPL-2.0 license short name definiton in headers.
> > >   - Add empty line after MTD_ENTRY_NUMBERS define.
> > >
> > > Links:
> > >
> > >   - [1] https://lore.kernel.org/all/20240227100441.1811047-1-avromanov@salutedevices.com/
> > >   - [2] https://lore.kernel.org/all/20240227100441.1811047-5-avromanov@salutedevices.com/
> > >   - [3] https://lore.kernel.org/u-boot/20240403114047.84030-1-heinrich.schuchardt@canonical.com/T/#u
> > >
> > > Alexey Romanov (3):
> > >   disk: support MTD partitions
> > >   drivers: introduce mtdblock abstraction
> > >   spinand: bind mtdblock
> > >
> > >  disk/part.c                 |   3 +-
> > >  drivers/block/blk-uclass.c  |   1 +
> > >  drivers/mtd/Kconfig         |   1 +
> > >  drivers/mtd/Makefile        |   1 +
> > >  drivers/mtd/mtdblock.c      | 227 ++++++++++++++++++++++++++++++++++++
> > >  drivers/mtd/mtdpart.c       |  69 +++++++++++
> > >  drivers/mtd/nand/spi/core.c |  20 ++++
> > >  include/linux/mtd/mtd.h     |  12 ++
> > >  include/part.h              |   3 +
> > >  9 files changed, 336 insertions(+), 1 deletion(-)
> > >  create mode 100644 drivers/mtd/mtdblock.c
> > >
> > > --
> > > 2.34.1
> > >
> >
> > --
> > Thank you,
> > Alexey
> 
> 
> 
> -- 
> Michael Nazzareno Trimarchi
> Co-Founder & Chief Executive Officer
> M. +39 347 913 2170
> michael@amarulasolutions.com
> __________________________________
> 
> Amarula Solutions BV
> Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
> T. +31 (0)85 111 9172
> info@amarulasolutions.com
> www.amarulasolutions.com

-- 
Thank you,
Alexey

      reply	other threads:[~2024-05-06 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 10:58 [PATCH v3 0/3] Introduce mtdblock device Alexey Romanov
2024-04-04 10:58 ` [PATCH v3 1/3] disk: support MTD partitions Alexey Romanov
2024-04-04 10:58 ` [PATCH v3 2/3] drivers: introduce mtdblock abstraction Alexey Romanov
2024-04-04 10:58 ` [PATCH v3 3/3] spinand: bind mtdblock Alexey Romanov
2024-04-11 16:09 ` [PATCH v3 0/3] Introduce mtdblock device Alexey Romanov
2024-04-11 16:14   ` Michael Nazzareno Trimarchi
2024-05-06 13:56     ` Alexey Romanov [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=20240506135607.aprjqn7uyng2jgp5@cab-wsm-0029881 \
    --to=avromanov@salutedevices.com \
    --cc=abdellatif.elkhlifi@arm.com \
    --cc=bmeng@tinylab.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=dunaev@tecon.ru \
    --cc=frieder.schrempf@kontron.de \
    --cc=hs@denx.de \
    --cc=jagan@amarulasolutions.com \
    --cc=jbx6244@gmail.com \
    --cc=joe.hershberger@ni.com \
    --cc=jpewhacker@gmail.com \
    --cc=kernel@sberdevices.ru \
    --cc=kever.yang@rock-chips.com \
    --cc=kmpark@infradead.org \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=michael@amarulasolutions.com \
    --cc=mikhail.kshevetskiy@iopsys.eu \
    --cc=sjg@chromium.org \
    --cc=tobias@waldekranz.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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).