Devicetree
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org>
To: jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org
Subject: ARM machine specific DT probing
Date: Wed, 08 Sep 2010 15:43:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1009081523500.19366@xanadu.home> (raw)

While reviewing the ARM DT patches I've come to a misunderstanding of 
how the specific machine support is meant to be matched with DT.

What Jeremy did is to add a probe_dt method in the mdesc structure, and 
then the core is calling them in sequence until one of them returns 
success.

now, the "compatible" property is explained here:

http://devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property

>From my understanding, this could allow for a kernel that doesn't yet 
support the specifics of a particular board to still be able to work 
using basic common support.  But for this to work, wouldn't it be 
necessary for the core code to try to find the best match itself rather 
than letting each machine's  probe_dt decide on their own?


Nicolas

             reply	other threads:[~2010-09-08 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 19:43 Nicolas Pitre [this message]
     [not found] ` <alpine.LFD.2.00.1009081523500.19366-QuJgVwGFrdf/9pzu0YdTqQ@public.gmane.org>
2010-09-09  1:07   ` ARM machine specific DT probing Jeremy Kerr
2010-09-13  2:20     ` David Gibson
2010-09-13  5:30       ` Jeremy Kerr
2010-09-13  6:03         ` David Gibson
2010-09-16 17:40           ` Grant Likely
     [not found]             ` <20100916174020.GA7550-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-09-16 22:56               ` Scott Wood
     [not found]                 ` <20100916175617.7e36ed0e-1MYqz8GpK7RekFaExTCHk1jVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2010-09-20  1:35                   ` David Gibson

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=alpine.LFD.2.00.1009081523500.19366@xanadu.home \
    --to=nico-vtqb6hgkxmzr7s880joybq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    /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