U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX needs prior to DM conversion?
Date: Mon, 26 Nov 2018 12:00:29 +0100	[thread overview]
Message-ID: <afb5732c-bc32-c5a9-ecce-b71bdc72032b@denx.de> (raw)
In-Reply-To: <20181123194555.GH11247@bill-the-cat>

Hi Tom,

On 23/11/18 20:45, Tom Rini wrote:
> Hey guys,
> 
> So, from the BLK conversion thread, I'd like to bring up and ask what
> needs to happen before we can consider the i.MX families ready for bulk
> conversion to using DM (and OF_CONTROL and BLK and ..) at least in full
> U-Boot.  I know some things have been converted already and some
> platforms do make use of it, but we have some missing items too.  For
> example, both drivers/mmc/fsl_esdhc.c

I guessed fsl_esdhc was already converted.

> and drivers/ata/dwc_ahsata.c

Right.

> need
> conversion.  Is anyone able to start on either of these soon?  Thanks!

This depends on the status of my current projects - I have not at the
moment a project that allows me to work on these topics, so I guess I
cannot be active (very) soon. But things change steadily, who knows...

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2018-11-26 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 19:45 [U-Boot] i.MX needs prior to DM conversion? Tom Rini
2018-11-26 11:00 ` Stefano Babic [this message]
2018-11-27  8:05   ` Wolfgang Denk
2018-11-27 12:17     ` 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=afb5732c-bc32-c5a9-ecce-b71bdc72032b@denx.de \
    --to=sbabic@denx.de \
    --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