public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] is it mandatory for SPL to support DM
Date: Mon, 25 May 2020 13:32:08 -0400	[thread overview]
Message-ID: <20200525173208.GA12717@bill-the-cat> (raw)
In-Reply-To: <CAMty3ZAMtz5T8DZrnSb-p6F_JF9Z_fLOj8cDdFXVo7adOKqyPg@mail.gmail.com>

On Mon, May 25, 2020 at 10:58:12PM +0530, Jagan Teki wrote:
> On Mon, May 25, 2020 at 9:06 PM Simon Glass <sjg@chromium.org> wrote:
> >
> > Hi,
> >
> > On Mon, 25 May 2020 at 04:35, Marek Vasut <marex@denx.de> wrote:
> > >
> > > On 5/25/20 10:44 AM, Jagan Teki wrote:
> > > > SPL has a foot-print constraint, so fully switching a particular
> > > > subsystem like SPI or SPI Flash to DM would increase the size of it.
> > > >
> > > > Possible areas to look at are (assume SPL_DM supported)
> > > > 1) platdata
> > > > 2) implement board or platform specific spl device driver which
> > > > bypassed the actual framework ex: spl_spi_sunxi.c
> > > >
> > > > Do we have any other solutions? or any arguments on above step 2?
> > >
> > > SPL does not need to support DM until the size problem is solved.
> >
> > I don't think the problem will ever be 'solved'. It is an ongoing battle.
> >
> > But as it happens I've just sent a proposal for tiny-dm that I think will help.
> >
> > Jagan, which board are you trying to convert? If you are trying to
> > convert SPI flash, I think we need to remove the legacy code first.
> 
> These are the partially dm converted drivers, so boards which are
> using can eventually need a dm spi switch.
> 
>         drivers/spi/fsl_dspi.c
>         drivers/spi/kirkwood_spi.c
>         drivers/spi/mxc_spi.c
>         drivers/spi/mxs_spi.c
>         drivers/spi/omap3_spi.c
>         drivers/spi/sh_qspi.c
> 
> I'm looking for proper options along with removal of some legacy code,
> and tiny-dm.

For the number of about to be year past published deadline (which has
been extended at times to get to that point even) boards, I think we
need to start by dropping boards.  Then we can see what makes sense
moving forward.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200525/69ca42b2/attachment.sig>

  reply	other threads:[~2020-05-25 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  8:44 [U-Boot] is it mandatory for SPL to support DM Jagan Teki
2020-05-25 10:35 ` Marek Vasut
2020-05-25 15:36   ` Simon Glass
2020-05-25 15:43     ` Marek Vasut
2020-05-25 15:48       ` Simon Glass
2020-05-25 15:56         ` Marek Vasut
2020-05-25 16:59           ` Simon Glass
2020-05-25 19:06             ` Marek Vasut
2020-05-26 12:36               ` Simon Glass
2020-05-25 17:28     ` Jagan Teki
2020-05-25 17:32       ` Tom Rini [this message]
2020-05-25 19:07         ` Marek Vasut
2020-05-25 19:28           ` Tom Rini
2020-05-25 19:48             ` Marek Vasut
2020-05-25 19:55               ` Tom Rini
2020-05-25 19:59                 ` Marek Vasut
2020-05-25 20:00                   ` 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=20200525173208.GA12717@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox