From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Migrating iMX LCDIF drivers to Driver Model
Date: Tue, 16 Apr 2019 14:31:14 +0200 [thread overview]
Message-ID: <20190416143114.645dd5cc@crub> (raw)
In-Reply-To: <CAByghJaM8VqFXe3LWEoRZ0NrSb_cXe+Av1ZRMSaPKFShqWmFrw@mail.gmail.com>
Hi Igor,
On Tue, 16 Apr 2019 12:04:41 +0000
Igor Opaniuk igor.opaniuk at toradex.com wrote:
...
> So there are 2 questions spinning in my mind:
> 1) In case if you are maybe aware, if there were any intentions to do
> this migration before? (maybe someone asked similar questions or even
> send some patches, but didn't manage to upstream that; or did similar
> stuff in some downstream U-boot forks, whatever). Unfortunately I
> can't any information regarding this in U-boot ML archives .
I'm not aware of any activity migrating this driver to DM_VIDEO.
Patches welcome.
> 2) Will it be OK if I introduce a brand new mxsfb driver (ported from
> Linux), which will be used only when U-boot is built with
> CONFIG_DM_VIDEO enabled? Existing mxsfb will be left as it is, so I
> can be removed easily when full migration to DM is done for all boards
> that are using this driver.
I have no objections. However I don't know how big is the Linux mxsfb
driver, maybe we could reduce not needed code to keep the code size
smaller.
--
Anatolij
next prev parent reply other threads:[~2019-04-16 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 12:04 [U-Boot] [RFC] Migrating iMX LCDIF drivers to Driver Model Igor Opaniuk
2019-04-16 12:31 ` Anatolij Gustschin [this message]
2019-04-16 12:58 ` Igor Opaniuk
2019-04-16 12:34 ` Jagan Teki
2019-04-16 12:46 ` Igor Opaniuk
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 23:28 Peng Fan
2019-04-16 23:36 ` Simon Glass
2019-04-24 18:15 ` Fabio Estevam
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=20190416143114.645dd5cc@crub \
--to=agust@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 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.