public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Alexander Sverdlin <alexander.sverdlin@nokia.com>
Cc: York Sun <yorksun@freescale.com>,
	wsa@the-dreams.de, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org,
	Peter Korsgaard <peter.korsgaard@barco.com>
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@nokia.com>

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


  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
2015-06-17  8:54 ` Paul Bolle
2015-06-17 15:00   ` Alexander Sverdlin
2015-06-17 16:03     ` Paul Bolle
2015-06-18  7:40       ` Alexander Sverdlin
2015-06-18  8:08         ` Paul Bolle [this message]
2015-06-18  9:04           ` Alexander Sverdlin
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
2015-06-17 16:43   ` York Sun
2015-06-18  7:58     ` Alexander Sverdlin
2015-08-15 20:23 ` Wolfram Sang
2015-08-17 16:37   ` York Sun
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@tiscali.nl \
    --cc=alexander.sverdlin@nokia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.korsgaard@barco.com \
    --cc=wsa@the-dreams.de \
    --cc=yorksun@freescale.com \
    /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