linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rafael.j.wysocki@intel.com (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Convert smsc911x to use ACPI as well as DT
Date: Wed, 23 Sep 2015 22:51:54 +0200	[thread overview]
Message-ID: <560310EA.2070805@intel.com> (raw)
In-Reply-To: <1443033714.74600.18.camel@infradead.org>

On 9/23/2015 8:41 PM, David Woodhouse wrote:
> On Wed, 2015-08-12 at 17:06 -0500, Jeremy Linton wrote:
>>   
>> +static const struct acpi_device_id smsc911x_acpi_match[] = {
>> +       { "ARMH9118", 0 },
>> +       { }
>> +};
>> +MODULE_DEVICE_TABLE(acpi, smsc911x_acpi_match);
>> +
>>   static struct platform_driver smsc911x_driver = {
>>          .probe = smsc911x_drv_probe,
>>          .remove = smsc911x_drv_remove,
>> @@ -2661,6 +2656,7 @@ static struct platform_driver smsc911x_driver =
>> {
>>                  .name   = SMSC_CHIPNAME,
>>                  .pm     = SMSC911X_PM_OPS,
>>                  .of_match_table = of_match_ptr(smsc911x_dt_ids),
>> +               .acpi_match_table = ACPI_PTR(smsc911x_acpi_match),
>>          },
>>   };
> Hm, surely you shouldn't need this part? If the ACPI device has a HID
> of PRP0001, and an appropriate "compatible" property, then it ought to
> be loaded anyway. If that doesn't work, we should fix that.

But if the device ID is assigned already, why would it hurt to actually 
use it?

Thanks,
Rafael

  reply	other threads:[~2015-09-23 20:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 22:06 [PATCH 0/2] Enable smsc911x for use with ACPI Jeremy Linton
2015-08-12 22:06 ` [PATCH 1/2] Add a matching set of device_ functions for determining mac/phy Jeremy Linton
2015-08-12 22:13   ` Florian Fainelli
2015-08-14 15:55     ` Jeremy Linton
2015-08-13 11:57   ` Robin Murphy
2015-08-13 14:24     ` Jeremy Linton
2015-08-12 22:06 ` [PATCH 2/2] Convert smsc911x to use ACPI as well as DT Jeremy Linton
2015-08-13  8:27   ` Graeme Gregory
2015-08-13  9:01     ` Lorenzo Pieralisi
2015-08-13  9:38       ` Graeme Gregory
2015-08-13 10:30         ` Lorenzo Pieralisi
2015-09-09 16:10   ` Marc Zyngier
2015-09-23 17:22     ` Jeremy Linton
2015-09-23 17:46       ` Marc Zyngier
2015-09-23 17:57       ` Sudeep Holla
2015-09-24  9:20         ` Catalin Marinas
2015-11-02 15:48     ` Jeremy Linton
2015-09-23 18:41   ` David Woodhouse
2015-09-23 20:51     ` Rafael J. Wysocki [this message]
2015-09-23 21:03       ` David Woodhouse
2015-09-23 23:56         ` Hanjun Guo
2015-09-24  8:16           ` David Woodhouse
2015-09-24 10:31             ` Catalin Marinas
2015-09-24 11:52               ` David Woodhouse
2015-09-24 14:01                 ` Lorenzo Pieralisi
2015-09-24 14:31                   ` David Woodhouse
2015-09-24 15:15                 ` Catalin Marinas
2015-09-24 18:10                   ` David Woodhouse
2015-09-25 15:28                     ` Catalin Marinas
2015-09-26  2:16                       ` Rafael J. Wysocki
2015-09-26 15:20                       ` David Woodhouse
2015-10-01  2:23                       ` Al Stone
2015-10-06  0:20                         ` Charles Garcia-Tobin
2015-10-06 11:08                           ` David Woodhouse
2015-10-08  0:11                             ` Rafael J. Wysocki
2015-08-14  0:00 ` [PATCH 0/2] Enable smsc911x for use with ACPI David Miller

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=560310EA.2070805@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).