From: Brian Norris <computersforpeace@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 03/18] mtd: dataflash: Export OF module alias information
Date: Fri, 21 Aug 2015 15:47:14 -0700 [thread overview]
Message-ID: <20150821224714.GD81844@google.com> (raw)
In-Reply-To: <55D65B72.2050006@osg.samsung.com>
Hi Javier,
On Fri, Aug 21, 2015 at 12:57:54AM +0200, Javier Martinez Canillas wrote:
> On 08/21/2015 12:34 AM, Brian Norris wrote:
> > On Fri, Aug 21, 2015 at 12:13:34AM +0200, Javier Martinez Canillas wrote:
> >> So this patch really is a no-op right now and is not fixing anything.
> >> As long as the driver has a MODULE_DEVICE_TABLE(spi,...), things will
> >
> > This driver does not have a MODULE_DEVICE_TABLE() at all, nor does it
> > use spi_device_id. So, it is currently broken for the module use case.
> >
>
> That is correct but also that does not mean that this patch will fix
> module autoloading right now. It will though once the SPI core is
> changed to report a OF type module alias.
Ah, thanks for the patience. I missed the point that it will still be
broken.
> So what about something along this lines?
>
> mtd: dataflash: Export OF module alias information
>
> The SPI core currently reports the MODALIAS uevent as "spi:<modalias>"
> even for SPI devices that were registered by OF.
>
> That means the OF module alias exported by MODULE_OF_TABLE(of,...) is
> currently not used and user-space has no way to autoload this module.
>
> But is still a good practice to add the OF module alias information
nit: s/is/it is/
> into the kernel module even when currently is unused so once the SPI
ditto
> core is changed to report a correct OF modalias uevent, module
> autoloading will be working for this driver.
Otherwise, looks good. I'll either patch in this commit message, or
await v2. Your call.
Regards,
Brian
next prev parent reply other threads:[~2015-08-21 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 7:07 [PATCH 00/18] Export SPI and OF module aliases in missing drivers Javier Martinez Canillas
2015-08-20 7:07 ` [PATCH 03/18] mtd: dataflash: Export OF module alias information Javier Martinez Canillas
2015-08-20 21:54 ` Brian Norris
2015-08-20 22:13 ` Javier Martinez Canillas
2015-08-20 22:34 ` Brian Norris
2015-08-20 22:57 ` Javier Martinez Canillas
2015-08-21 22:47 ` Brian Norris [this message]
2015-08-22 0:26 ` Javier Martinez Canillas
2015-08-22 1:05 ` Brian Norris
2015-08-22 1:10 ` Javier Martinez Canillas
2015-08-20 21:11 ` [PATCH 00/18] Export SPI and OF module aliases in missing drivers Brian Norris
2015-08-20 21:50 ` Javier Martinez Canillas
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=20150821224714.GD81844@google.com \
--to=computersforpeace@gmail.com \
--cc=broonie@kernel.org \
--cc=dwmw2@infradead.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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