From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH 2/2] gpio: ts4800: Fix module autoload
Date: Fri, 21 Oct 2016 10:32:14 -0300 [thread overview]
Message-ID: <cca95b94-82fc-ff40-76af-bfce8db9bfb4@osg.samsung.com> (raw)
In-Reply-To: <CACRpkdZcopStg7B8si97gLzCvE1y4_VYXFjOsbw=gt+hX6pdfQ@mail.gmail.com>
Hello Linus,
On 10/21/2016 09:55 AM, Linus Walleij wrote:
> On Tue, Oct 18, 2016 at 10:44 PM, 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-ts4800.ko | grep alias
>> $
>>
>> After this patch:
>>
>> $ modinfo drivers/gpio/gpio-ts4800.ko | grep alias
>> alias: of:N*T*Ctechnologic,ts4800-gpioC*
>> alias: of:N*T*Ctechnologic,ts4800-gpio
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> Patch applied for fixes.
>
Thanks, I guess this also applies to Patch 1/2?
> Yours,
> Linus Walleij
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-10-21 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:44 [PATCH 1/2] gpio: ath79: " 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 [this message]
2016-10-19 17:10 ` [PATCH 1/2] gpio: ath79: " Alban
2016-10-23 22:23 ` 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=cca95b94-82fc-ff40-76af-bfce8db9bfb4@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=gnurou@gmail.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
all inboxes | Powered by JetHome®