All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,1/2] spi: ti_qspi: Drop non DM code
Date: Fri, 12 Apr 2019 07:49:36 -0400	[thread overview]
Message-ID: <20190412114936.GA3130@bill-the-cat> (raw)
In-Reply-To: <20190211090536.23953-2-vigneshr@ti.com>

On Mon, Feb 11, 2019 at 02:35:35PM +0530, Vignesh R wrote:

> Now that all boards using TI QSPI have moved to DM and DT, drop non DM
> code completely.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
> ---
>  drivers/spi/Kconfig            |  12 +-
>  drivers/spi/Makefile           |   2 +-
>  drivers/spi/ti_qspi.c          | 231 ++++++---------------------------
>  include/configs/am43xx_evm.h   |   2 -
>  include/configs/am57xx_evm.h   |   2 -
>  include/configs/cl-som-am57x.h |   1 -
>  include/configs/cm_t43.h       |   1 -
>  include/configs/dra7xx_evm.h   |   2 -
>  scripts/config_whitelist.txt   |   2 -
>  9 files changed, 45 insertions(+), 210 deletions(-)

The problem is that cl-som-am57x isn't converted to enabling CONFIG_DM
at all.  Uri, is this something that's on your current TODO list?
Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190412/8740bc70/attachment.sig>

  parent reply	other threads:[~2019-04-12 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  9:05 [U-Boot] [PATCH 0/2] ti_qspi: Move to spi-mem framework Vignesh R
2019-02-11  9:05 ` [U-Boot] [PATCH 1/2] spi: ti_qspi: Drop non DM code Vignesh R
2019-02-11 22:41   ` Tom Rini
2019-04-12 11:49   ` Tom Rini [this message]
2019-04-12 12:21     ` [U-Boot] [U-Boot,1/2] " Raghavendra, Vignesh
2019-04-12 12:33       ` Tom Rini
2019-02-11  9:05 ` [U-Boot] [PATCH 2/2] spi: ti_qspi: Convert to spi-mem ops Vignesh R
2019-02-11 22:41   ` Tom Rini

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=20190412114936.GA3130@bill-the-cat \
    --to=trini@konsulko.com \
    --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 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.