From: Alban <albeu@free.fr>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Aban Bedel <albeu@free.fr>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH 1/2] gpio: ath79: Fix module autoload
Date: Wed, 19 Oct 2016 19:10:22 +0200 [thread overview]
Message-ID: <20161019191022.7079044b@tock> (raw)
In-Reply-To: <1476823442-31104-1-git-send-email-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Tue, 18 Oct 2016 17:44:01 -0300
Javier Martinez Canillas <javier@osg.samsung.com> wrote:
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias information using the MODULE_DEVICE_TABLE() macro.
>
> Before this patch:
>
> $ modinfo drivers/gpio/gpio-ath79.ko | grep alias
> $
>
> After this patch:
>
> $ modinfo drivers/gpio/gpio-ath79.ko | grep alias
> alias: of:N*T*Cqca,ar9340-gpioC*
> alias: of:N*T*Cqca,ar9340-gpio
> alias: of:N*T*Cqca,ar7100-gpioC*
> alias: of:N*T*Cqca,ar7100-gpio
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Acked-by: Aban Bedel <albeu@free.fr>
Alban
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-19 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:44 [PATCH 1/2] gpio: ath79: Fix module autoload Javier Martinez Canillas
2016-10-18 20:44 ` [PATCH 2/2] gpio: ts4800: " Javier Martinez Canillas
2016-10-21 12:55 ` Linus Walleij
2016-10-21 13:32 ` Javier Martinez Canillas
2016-10-19 17:10 ` Alban [this message]
2016-10-23 22:23 ` [PATCH 1/2] gpio: ath79: " Linus Walleij
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=20161019191022.7079044b@tock \
--to=albeu@free.fr \
--cc=gnurou@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).