All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Timur Tabi <timur@freescale.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Jon Smirl <jonsmirl@gmail.com>,
	linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
	liam.girdwood@wolfsonmicro.com
Subject: Re: [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers
Date: Mon, 14 Jul 2008 13:53:35 -0500	[thread overview]
Message-ID: <487BA0AF.10803@freescale.com> (raw)
In-Reply-To: <20080714184929.GJ25448@sirena.org.uk>

Mark Brown wrote:

>> The only problem with this is that the OF probing code in the kernel binds
>> drivers to device tree nodes.  So when a driver claims a node, no other driver
>> will be probed with it.
> 
>> So we can't have generic nodes that classify the motherboard and just let
>> everyone get probed on it.
> 
> My suggestion is that you change this for the root node. 

That's an interesting idea.

> It's already
> got the information required in there, it's just there's no way to use
> it to load modules at the minute.

Correct.

>  You could presumably read the
> information out of the device tree using existing APIs to check you're
> running on the right board once code is loaded?

Yes.  The driver <-> node binding is only for probing.  Any driver can scan the
entire tree at any time.

-- 
Timur Tabi
Linux kernel developer at Freescale

WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Timur Tabi <timur@freescale.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Jon Smirl <jonsmirl@gmail.com>,
	linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
	liam.girdwood@wolfsonmicro.com
Subject: Re: [alsa-devel] [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers
Date: Mon, 14 Jul 2008 13:53:35 -0500	[thread overview]
Message-ID: <487BA0AF.10803@freescale.com> (raw)
In-Reply-To: <20080714184929.GJ25448@sirena.org.uk>

Mark Brown wrote:

>> The only problem with this is that the OF probing code in the kernel binds
>> drivers to device tree nodes.  So when a driver claims a node, no other driver
>> will be probed with it.
> 
>> So we can't have generic nodes that classify the motherboard and just let
>> everyone get probed on it.
> 
> My suggestion is that you change this for the root node. 

That's an interesting idea.

> It's already
> got the information required in there, it's just there's no way to use
> it to load modules at the minute.

Correct.

>  You could presumably read the
> information out of the device tree using existing APIs to check you're
> running on the right board once code is loaded?

Yes.  The driver <-> node binding is only for probing.  Any driver can scan the
entire tree at any time.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-07-14 18:53 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-12  8:39 [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Grant Likely
2008-07-12  8:39 ` Grant Likely
2008-07-12  8:39 ` [PATCH v2 2/3] ALSA SoC: Add mpc5200-psc I2S driver Grant Likely
2008-07-14 12:10   ` Mark Brown
2008-07-14 12:10     ` [alsa-devel] " Mark Brown
2008-07-12  8:39 ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Grant Likely
2008-07-12  8:39   ` Grant Likely
2008-07-12 18:10   ` Mark Brown
2008-07-12 18:10     ` [alsa-devel] " Mark Brown
2008-07-12 18:14     ` Grant Likely
2008-07-12 18:14       ` [alsa-devel] " Grant Likely
2008-07-14 11:45   ` Mark Brown
2008-07-14 11:45     ` [alsa-devel] " Mark Brown
2008-07-18  6:29     ` Grant Likely
2008-07-18  6:29       ` [alsa-devel] " Grant Likely
2008-07-18 10:39       ` Mark Brown
2008-07-18 10:39         ` [alsa-devel] " Mark Brown
2008-07-15  7:57   ` dinesh
2008-07-15  7:57     ` [alsa-devel] " dinesh
2008-07-15 10:33     ` Mark Brown
2008-07-15 10:33       ` [alsa-devel] " Mark Brown
2008-07-15 12:38       ` dinesh
2008-07-15 12:38         ` [alsa-devel] " dinesh
2008-07-15 12:46         ` Mark Brown
2008-07-15 12:46           ` [alsa-devel] " Mark Brown
2008-07-16  9:05   ` WRITING AN SOC DRIVER WITHOUT DMA dinesh
2008-07-16  9:05     ` dinesh
2008-07-16 10:07     ` Nobin Mathew
2008-07-16 10:07       ` [alsa-devel] " Nobin Mathew
2008-07-16 10:13       ` dinesh
2008-07-16 10:13         ` [alsa-devel] " dinesh
2008-07-17  6:03         ` dinesh
2008-07-17  6:03           ` [alsa-devel] " dinesh
2008-07-17 10:56           ` Mark Brown
2008-07-17 10:56             ` [alsa-devel] " Mark Brown
2008-07-17 11:26             ` Nobin Mathew
2008-07-17 11:26               ` [alsa-devel] " Nobin Mathew
2008-07-17 12:05               ` Jon Smirl
2008-07-17 12:05                 ` [alsa-devel] " Jon Smirl
2008-07-17 16:02   ` [PATCH v2 3/3] ALSA SoC: Add Texas Instruments TLV320AIC26 codec driver Timur Tabi
2008-07-14 13:49 ` [PATCH v2 1/3] ALSA SoC: Add OpenFirmware helper for matching bus and codec drivers Mark Brown
2008-07-14 13:49   ` [alsa-devel] " Mark Brown
2008-07-14 14:13   ` Jon Smirl
2008-07-14 14:13     ` [alsa-devel] " Jon Smirl
2008-07-14 15:05     ` Mark Brown
2008-07-14 15:05       ` [alsa-devel] " Mark Brown
2008-07-14 16:14       ` Timur Tabi
2008-07-14 16:14         ` [alsa-devel] " Timur Tabi
2008-07-14 16:27         ` Grant Likely
2008-07-14 16:27           ` [alsa-devel] " Grant Likely
2008-07-14 16:53         ` Mark Brown
2008-07-14 16:53           ` [alsa-devel] " Mark Brown
2008-07-14 17:21           ` Grant Likely
2008-07-14 17:21             ` [alsa-devel] " Grant Likely
2008-07-14 18:36             ` Mark Brown
2008-07-14 18:36               ` [alsa-devel] " Mark Brown
2008-07-14 18:40               ` Timur Tabi
2008-07-14 18:40                 ` [alsa-devel] " Timur Tabi
2008-07-14 18:49                 ` Mark Brown
2008-07-14 18:49                   ` [alsa-devel] " Mark Brown
2008-07-14 18:53                   ` Timur Tabi [this message]
2008-07-14 18:53                     ` Timur Tabi
2008-07-14 22:28                 ` Grant Likely
2008-07-14 22:28                   ` [alsa-devel] " Grant Likely
2008-07-14 23:45                 ` Jon Smirl
2008-07-14 23:45                   ` [alsa-devel] " Jon Smirl
2008-07-15 10:13                   ` Mark Brown
2008-07-15 10:13                     ` [alsa-devel] " Mark Brown
2008-07-15 13:08                     ` Jon Smirl
2008-07-15 13:08                       ` [alsa-devel] " Jon Smirl
2008-07-15 14:04                       ` Mark Brown
2008-07-15 14:04                         ` [alsa-devel] " Mark Brown
2008-07-14 15:51     ` Timur Tabi
2008-07-14 15:51       ` [alsa-devel] " Timur Tabi
2008-07-14 17:06   ` Grant Likely
2008-07-14 17:06     ` [alsa-devel] " Grant Likely
2008-07-14 17:16     ` Mark Brown
2008-07-14 17:16       ` [alsa-devel] " Mark Brown
2008-07-14 17:22       ` Grant Likely
2008-07-14 17:22         ` [alsa-devel] " Grant Likely
2008-07-18  7:17       ` Grant Likely
2008-07-18  7:17         ` [alsa-devel] " Grant Likely
2008-07-18 10:00         ` Mark Brown
2008-07-18 10:00           ` [alsa-devel] " Mark Brown
2008-07-18 14:59         ` Timur Tabi
2008-07-18 14:59           ` [alsa-devel] " Timur Tabi
2008-07-14 14:16 ` Anton Vorontsov
2008-07-14 14:16   ` Anton Vorontsov
2008-07-14 17:11   ` Grant Likely

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=487BA0AF.10803@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jonsmirl@gmail.com \
    --cc=liam.girdwood@wolfsonmicro.com \
    --cc=linuxppc-dev@ozlabs.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 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.