From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mmc: sdhci-acpi: add SDHCI ACPI driver
Date: Fri, 23 Nov 2012 11:44:06 +0200 [thread overview]
Message-ID: <20121123094406.GS3867@intel.com> (raw)
In-Reply-To: <1353573830-13006-4-git-send-email-adrian.hunter@intel.com>
On Thu, Nov 22, 2012 at 10:43:50AM +0200, Adrian Hunter wrote:
> +static int __devinit sdhci_acpi_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + acpi_handle handle = dev->acpi_handle;
This is not going to work anymore, you'll have to use ACPI_HANDLE(dev) for
this (there was a new macro introduced with the struct acpi_dev_node).
> + struct acpi_device *device;
> + struct sdhci_acpi_host *c;
> + struct sdhci_host *host;
> + struct resource *iomem;
> + resource_size_t len;
> + const char *hid;
> + int err;
> +
> + if (acpi_bus_get_device(handle, &device))
> + return -ENODEV;
> +
> + if (acpi_bus_get_status(device) || !device->status.present)
> + return -ENODEV;
This is a bit redundant as the platform code already checks whether the
device is present or not and only creates the platform device in case it is
present.
next prev parent reply other threads:[~2012-11-23 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:43 [PATCH 0/3] Add SDHCI ACPI driver Adrian Hunter
2012-11-22 8:43 ` [PATCH 1/3] PNPACPI: exclude SDHCI devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 2/3] ACPI: add SDHCI to ACPI platform devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 3/3] mmc: sdhci-acpi: add SDHCI ACPI driver Adrian Hunter
2012-11-23 9:44 ` Mika Westerberg [this message]
2012-11-22 13:55 ` [PATCH 0/3] Add " Chris Ball
2012-11-22 14:46 ` Adrian Hunter
2012-11-22 21:24 ` Rafael J. Wysocki
2012-11-23 9:34 ` Mika Westerberg
2012-11-23 10:13 ` Adrian Hunter
2012-11-23 10:50 ` Rafael J. Wysocki
2012-11-23 10:23 ` Adrian Hunter
2012-11-23 10:51 ` Rafael J. Wysocki
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=20121123094406.GS3867@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=cjb@laptop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
/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).