From: "liaochen (A)" <liaochen4@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<justin.chen@broadcom.com>, <alcooperx@gmail.com>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH -next] usb: bdc: fix module autoloading
Date: Thu, 15 Aug 2024 09:27:34 +0800 [thread overview]
Message-ID: <1ac3259a-813c-4c09-a24d-653207288d7c@huawei.com> (raw)
In-Reply-To: <2024081423-trapdoor-alabaster-24a7@gregkh>
On 2024/8/14 12:36, Greg KH wrote:
> On Wed, Aug 14, 2024 at 03:04:43AM +0000, Liao Chen wrote:
>> Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
>> based on the alias from of_device_id table.
>>
>> Signed-off-by: Liao Chen <liaochen4@huawei.com>
>> ---
>> drivers/usb/gadget/udc/bdc/bdc_core.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c b/drivers/usb/gadget/udc/bdc/bdc_core.c
>> index 35a652807fca..5149e2b7f050 100644
>> --- a/drivers/usb/gadget/udc/bdc/bdc_core.c
>> +++ b/drivers/usb/gadget/udc/bdc/bdc_core.c
>> @@ -639,6 +639,7 @@ static const struct of_device_id bdc_of_match[] = {
>> { .compatible = "brcm,bdc" },
>> { /* sentinel */ }
>> };
>> +MODULE_DEVICE_TABLE(of, bdc_of_match);
>>
>> static struct platform_driver bdc_driver = {
>> .driver = {
>> --
>> 2.34.1
>>
>>
>
> What commit id does this fix?
Hi, this patch fixes commit 8ac1685bf911f70aea6de67b3db5674c3ea112f1
("usb: bdc: hook a quick Device Tree compatible string"), which allows
bdc device probing.
Thanks,
Chen
next prev parent reply other threads:[~2024-08-15 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 3:04 [PATCH -next] usb: bdc: fix module autoloading Liao Chen
2024-08-14 4:36 ` Greg KH
2024-08-15 1:27 ` liaochen (A) [this message]
2024-08-15 4:25 ` Florian Fainelli
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=1ac3259a-813c-4c09-a24d-653207288d7c@huawei.com \
--to=liaochen4@huawei.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=justin.chen@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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