[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1437056116.28351.19.camel@tiscali.nl>
Date: Thu, 16 Jul 2015 16:15:16 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Mark Brown <broonie@...nel.org>
Cc: Xing Zheng <zhengxing@...k-chips.com>, dgreid@...omium.org,
dianders@...omium.org, heiko@...ech.de, sonnyrao@...omium.org,
linux-rockchip@...ts.infradead.org,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090
codec
On do, 2015-07-16 at 13:55 +0100, Mark Brown wrote:
> No, in that case you've not understood what the MODULE_ALIAS is
> for. It's there so that userspace knows which module to load if it
> gets
> a device with no driver, it goes in the driver not in the code
> registering the device.
That's exactly how I understood MODULE_ALIAS() to work.
And it works, in short, because a platform device fires a
"MODALIAS=platform:[...]" uevent when it's created. And userspace uses
that uevent to load the module carrying that alias.
Let's put it this was. If one does
sudo find /sys -perm -o=r -name uevent -exec grep -H MODALIAS=platform: {} \;
or
sudo find /sys -perm -o=r -name modalias -exec grep -H platform: {} \;
(both lists should be similar)
on the systems this patch is targeting, will
platform:rockchip-snd-max98090
then show up?
Thanks,
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists