From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ata: ahci_platform: Add ACPI support for AMD Seattle SATA controller
Date: Fri, 12 Sep 2014 10:14:18 +0200 [thread overview]
Message-ID: <5412AB5A.3090801@redhat.com> (raw)
In-Reply-To: <CAOesGMh_Ku-pReg5LHVFvRM0-s_zEO4rgAvaD5rv-eTfPD71Yw@mail.gmail.com>
Hi,
On 09/11/2014 10:17 PM, Olof Johansson wrote:
> On Tue, Sep 9, 2014 at 1:37 PM, <suravee.suthikulpanit@amd.com> wrote:
>> From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>
>> This patch adds ACPI support for non-PCI SATA contoller in ahci_platform driver.
>> It adds ACPI matching table in ahci_platform to support AMD Seattle SATA controller
>> with following ASL structure in DSDT:
>>
>> Device (SATA0)
>> {
>> Name(_HID, "AMDI0600") // Seattle AHSATA
>> Name (_CCA, 1) // Cache-coherent controller
>> Name (_CRS, ResourceTemplate ()
>> {
>> Memory32Fixed (ReadWrite, 0xE0300000, 0x00010000)
>> Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive,,,) { 387 }
>> })
>> }
>>
>> Since ATA driver should not require PCI support for ATA_ACPI,
>> this patch also removes dependency in the driver/ata/Kconfig.
>>
>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>> ---
>> drivers/ata/Kconfig | 2 +-
>> drivers/ata/ahci_platform.c | 13 +++++++++++++
>> 2 files changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
>> index e1b9278..f2e6c9e 100644
>> --- a/drivers/ata/Kconfig
>> +++ b/drivers/ata/Kconfig
>> @@ -48,7 +48,7 @@ config ATA_VERBOSE_ERROR
>>
>> config ATA_ACPI
>> bool "ATA ACPI Support"
>> - depends on ACPI && PCI
>> + depends on ACPI
>> default y
>> help
>> This option adds support for ATA-related ACPI objects.
>> diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
>> index f61ddb9..3499bab 100644
>> --- a/drivers/ata/ahci_platform.c
>> +++ b/drivers/ata/ahci_platform.c
>> @@ -20,6 +20,9 @@
>> #include <linux/platform_device.h>
>> #include <linux/libata.h>
>> #include <linux/ahci_platform.h>
>> +#ifdef CONFIG_ATA_ACPI
>> +#include <linux/acpi.h>
>> +#endif
>> #include "ahci.h"
>>
>> static const struct ata_port_info ahci_port_info = {
>> @@ -87,6 +90,13 @@ static const struct of_device_id ahci_of_match[] = {
>> };
>> MODULE_DEVICE_TABLE(of, ahci_of_match);
>>
>> +#ifdef CONFIG_ATA_ACPI
>> +static const struct acpi_device_id ahci_acpi_match[] = {
>> + { "AMDI0600", 0 }, /* AMD Seattle AHCI */
>> + { },
>> +};
>> +#endif
>> +
>> static struct platform_driver ahci_driver = {
>> .probe = ahci_probe,
>> .remove = ata_platform_remove_one,
>> @@ -94,6 +104,9 @@ static struct platform_driver ahci_driver = {
>> .name = "ahci",
>> .owner = THIS_MODULE,
>> .of_match_table = ahci_of_match,
>> +#ifdef CONFIG_ATA_ACPI
>> + .acpi_match_table = ACPI_PTR(ahci_acpi_match),
>> +#endif
>
> The whole point of having ACPI_PTR() is to avoid having ifdefs like
> these. The structure member is always there, so there's no need to
> have it conditionally compiled out.
>
> Come to think of it, the match table should be under CONFIG_ACPI
> instead -- why do a separate config option just for this?
To clarify this for people like me who were under the impression
that ACPI_PTR() does some kind of cast, this is the definition
of ACPI_PTR:
#ifdef CONFIG_ACPI
#define ACPI_PTR(_ptr) (_ptr)
#else
#define ACPI_PTR(_ptr) (NULL)
#endif
Regards,
Hans
>
>
> -Olof
>
next prev parent reply other threads:[~2014-09-12 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 20:37 [PATCH] ata: ahci_platform: Add ACPI support for AMD Seattle SATA controller suravee.suthikulpanit at amd.com
2014-09-10 10:11 ` Hans de Goede
2014-09-11 20:17 ` Olof Johansson
2014-09-12 8:14 ` Hans de Goede [this message]
2014-09-28 21:51 ` Suravee Suthikulpanit
2014-09-29 18:16 ` Arnd Bergmann
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=5412AB5A.3090801@redhat.com \
--to=hdegoede@redhat.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).