All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] FDT driver initialization function declaration
Date: Tue, 10 Jul 2012 17:06:12 +0200	[thread overview]
Message-ID: <201207101706.12316.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ3Ac+ZWiJQoJBgnkYMitguvfhOi4+Q+=MZp4TbKOb3==g@mail.gmail.com>

Dear Simon Glass,

> Hi,
> 
> On Tue, Jul 10, 2012 at 3:05 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > Dear Michal Simek,
> > 
> > > Hi Simon, Wolfgang and others,
> > > 
> > > just want to open new topic about FDT driver initialization function
> > > declaration.
> > 
> > Ok, my few nits (with consideration of the DM stuff) ...
> > 1) Parsing the DTB is slowish
> 
> Yes, particularly early when (for example) the dcache is off and we can't
> store anything.

Well if you use DCache as DRAM ... but that's different tale ;-)

> One solution may be to have a simple way of picking out things that are
> needed early, and placing them in a simple C structure. Things like the
> serial base address (for console_init_f()) might fit this model.

This smells by global data. And picking them from the DTB is still complicated.

> Of course
> this needs a tool to do it. But the advantage is that everything is
> controlled from the fdt but without the performance penalty.
> 
> > 2) The DT can bind nicely with the DM, but if you could investigate
> > further and
> > help evaluating possible corner cases, that'd help a lot
> 
> I also only just became aware of your tree.

Hum, I did send out the email to many people, announcing this.

> It looks very promising and
> looks like it will solve a number of multi-device / initcall issues we have
> at present.

That's the point (right after making my life easier ;-) ). To squash the growing 
number of ad-hoc hacks trying to support multiple devices too.

> > 3) If you could go over the documentation and comment on it, that'd be
> > very nice.
> 
> 4) First patches for the DT shall land in next few weeks
> 
> 
> Do you mean land in mainline, or just in your tree?

I mean in the mailing list :)
 
> > Wolfgang, is it possible to somehow tag the DM patches so we can later
> > collect
> > these tagged patches to prove we did the amount of work to the university
> > committee? Or maybe simple "dm:" in the subject will suffice.
> > 
> > Best regards,
> > Marek Vasut
> 
> Regards,
> Simon

Best regards,
Marek Vasut

  reply	other threads:[~2012-07-10 15:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 10:23 [U-Boot] FDT driver initialization function declaration Michal Simek
2012-07-10 11:54 ` Wolfgang Denk
2012-07-10 12:24   ` Michal Simek
2012-07-10 13:00     ` Marek Vasut
2012-07-10 13:35       ` Michal Simek
2012-07-10 13:03     ` Wolfgang Denk
2012-07-10 13:12       ` Marek Vasut
2012-07-10 13:42         ` Michal Simek
2012-07-10 15:08           ` Marek Vasut
2012-07-11  6:16             ` Michal Simek
2012-07-11  9:52         ` Michal Simek
2012-07-12  7:10           ` [U-Boot] [U-Boot-DM] " Pavel Herrmann
2012-07-12  8:22             ` Michal Simek
2012-07-13 10:39               ` Tomas Hlavacek
2012-07-13 10:53                 ` Marek Vasut
2012-07-10 13:47       ` [U-Boot] " Michal Simek
2012-07-10 15:11         ` Marek Vasut
2012-07-11  6:11           ` Michal Simek
2012-07-13 10:32             ` Marek Vasut
2012-07-10 13:05 ` Marek Vasut
2012-07-10 13:12   ` Simon Glass
2012-07-10 15:06     ` Marek Vasut [this message]
2012-07-10 13:46   ` Wolfgang Denk
2012-07-10 13:18 ` Simon Glass
2012-07-10 13:49   ` Michal Simek
2012-07-14  6:49     ` Simon Glass

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=201207101706.12316.marex@denx.de \
    --to=marex@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.