From: Paul Bolle <pebolle-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
To: Alexander Sverdlin
<alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
Cc: York Sun <yorksun-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Peter Korsgaard
<peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] driver/i2c/mux: Add register based mux i2c-mux-reg
Date: Thu, 18 Jun 2015 10:08:21 +0200 [thread overview]
Message-ID: <1434614901.2385.27.camel@x220> (raw)
In-Reply-To: <558275F1.5020100-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
Hi Alexander,
On Thu, 2015-06-18 at 09:40 +0200, Alexander Sverdlin wrote:
> On 17/06/15 18:03, ext Paul Bolle wrote:
> >> You do not see the platform_device, because there are no users yet, put
> >> > this MODULE_ALIAS() is perfectly fine, it will allow automatic module loading
> >> > in non-DT case.
> > Do you mean that it will allow automatic module loading once the patch
> > that adds a struct platform_device with a "i2c-mux-reg" name lands?
>
> Any platform code which will register the platform_device will trigger uevent and
> udevd will be able to find the module with this macro. This is a legacy alternative
> to device-tree approach.
That means I've correctly figured out the purpose of this
MODULE_ALIAS("platform:" stuff. Because it might actually be documented
somewhere but I managed to not stumble on that documentation.
With that out of the way: am I right in thinking there's currently no
platform code that triggers that uevent for
"MODALIAS=platform:i2c-mux-reg"? Because if there's no struct
platform_device taking care of that I think this MODULE_ALIAS() should
not be added, not yet.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-06-18 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 17:28 [PATCH] driver/i2c/mux: Add register based mux i2c-mux-reg York Sun
[not found] ` <1434475692-4611-1-git-send-email-yorksun-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-06-17 8:54 ` Paul Bolle
2015-06-17 15:00 ` Alexander Sverdlin
[not found] ` <55818BAB.5090605-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-17 16:03 ` Paul Bolle
2015-06-18 7:40 ` Alexander Sverdlin
[not found] ` <558275F1.5020100-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 8:08 ` Paul Bolle [this message]
2015-06-18 9:04 ` Alexander Sverdlin
[not found] ` <5582899B.9030307-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 9:32 ` Paul Bolle
2015-06-18 9:42 ` Alexander Sverdlin
2015-06-18 9:55 ` Paul Bolle
2015-06-17 15:03 ` Alexander Sverdlin
[not found] ` <55818C3C.8000704-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-17 16:43 ` York Sun
[not found] ` <5581A3CA.4050805-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-06-18 7:58 ` Alexander Sverdlin
2015-08-15 20:23 ` Wolfram Sang
2015-08-17 16:37 ` York Sun
[not found] ` <55D20DC9.2060304-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-08-18 16:44 ` Wolfram Sang
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=1434614901.2385.27.camel@x220 \
--to=pebolle-iwqwacnznjzz+pzb47itoq@public.gmane.org \
--cc=alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.korsgaard-ob4gmnvZ1/cAvxtiuMwx3w@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
--cc=yorksun-KZfg59tc24xl57MIdRCFDg@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;
as well as URLs for NNTP newsgroup(s).