public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] spi: Zapping non-dm drivers, deadline: v2018.09
Date: Mon, 26 Feb 2018 21:08:47 +0100	[thread overview]
Message-ID: <20180226200847.GA27594@jerusalem> (raw)
In-Reply-To: <20180226172538.GU4311@bill-the-cat>

On Mon, Feb 26, 2018 at 12:25:38PM -0500, Tom Rini wrote:
> On Mon, Feb 26, 2018 at 08:28:45PM +0530, Jagan Teki wrote:
> 
> > Due to adding various new functionalities with SPI and SPI-FLASH
> > subsystems which are rounding in Mailing list for year+ [1] these long
> > term supporting spi driver which never seen any update with
> > driver-model conversion.
> > 
> > We support to write another stack code for supporting these legacy
> > stuff, but things become more difficult. So I'm finally giving
> > deadlines for these drivers to respective driver or board developers
> > to convert them as soon as possible.
> > 
> > PS: We all agree some special platforms has some difficulties with
> > dm-conversion let's discuss.
> > 
> > No dm conversion yet:
> > ----------------------------
> > drivers/spi/cf_spi.c

Ack. Starting the conversion as next task.

> > drivers/spi/fsl_espi.c
> > drivers/spi/lpc32xx_ssp.c
> > drivers/spi/mpc8xx_spi.c
> > drivers/spi/mpc8xxx_spi.c
> > drivers/spi/mxs_spi.c
> > drivers/spi/sh_qspi.c
> > drivers/spi/sh_spi.c
> > drivers/spi/soft_spi_legacy.c
> > 
> > 
> > Partially converted:
> > -------------------------
> > drivers/spi/atcspi200_spi.c
> > drivers/spi/atmel_spi.c
> > drivers/spi/davinci_spi.c
> > drivers/spi/fsl_dspi.c
> > drivers/spi/fsl_qspi.c
> > drivers/spi/kirkwood_spi.c
> > drivers/spi/mxc_spi.c
> > drivers/spi/omap3_spi.c
> > drivers/spi/ti_qspi.cM
> > 
> > I would like to see these legacy drivers with full dm-conversion or
> > zapped in v2018.09 version of U-Boot.
> > 
> > [1] http://u-boot.10912.n7.nabble.com/PATCH-v10-00-27-dm-Generic-MTD-Subsystem-with-SPI-NOR-interface-td315694i20.html
> 
> I've added a bunch of people to the Cc list.  I am in agreement with
> this idea.  I'd also rather not push the deadline here out further.
> Please, speak out if this is a problem, or if you'd like to drop some
> code / platforms.  Thanks all!
> 
> -- 
> Tom


Regards,
Angelo Dureghello

  parent reply	other threads:[~2018-02-26 20:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 14:58 [U-Boot] spi: Zapping non-dm drivers, deadline: v2018.09 Jagan Teki
2018-02-26 17:25 ` Tom Rini
2018-02-26 19:29   ` Marek Vasut
2018-02-27  6:31     ` Jagan Teki
2018-02-27 19:38       ` Marek Vasut
2018-02-26 20:08   ` Angelo Dureghello [this message]
2018-02-27 15:58   ` York Sun
2018-02-27 17:06     ` Jagan Teki
2018-02-27 22:02       ` Angelo Dureghello
2018-02-27 22:08         ` Tom Rini
2018-03-06 18:05         ` Jagan Teki

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=20180226200847.GA27594@jerusalem \
    --to=angelo@sysam.it \
    --cc=u-boot@lists.denx.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