From: Dongdong Liu <liudongdong3@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"Lorenzo Pieralisi" <Lorenzo.Pieralisi@arm.com>,
Tomasz Nowicki <tn@semihalf.com>, <wangzhou1@hisilicon.com>,
Pratyush Anand Thakur <pratyush.anand@gmail.com>,
Linux PCI <linux-pci@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jon Masters <jcm@redhat.com>, <gabriele.paoloni@huawei.com>,
<charles.chenxin@huawei.com>, Hanjun Guo <hanjun.guo@linaro.org>,
<linuxarm@huawei.com>
Subject: Re: [PATCH V5 1/2] PCI/ACPI: Provide acpi_get_rc_resources() for ARM64 platform
Date: Mon, 21 Nov 2016 16:19:25 +0800 [thread overview]
Message-ID: <41b92e95-7dcd-dbc5-8163-bac8cd3fb441@huawei.com> (raw)
In-Reply-To: <CAJZ5v0gMg6=ueeZz-PcNvuUW5ht=r8vn-gEru-2Cbx7HDCf+jA@mail.gmail.com>
Hi Rafael
Many Thanks for your review.
在 2016/11/19 6:00, Rafael J. Wysocki 写道:
> On Fri, Nov 18, 2016 at 10:22 AM, Dongdong Liu <liudongdong3@huawei.com> wrote:
>> The acpi_get_rc_resources() is used to get the RC register address that can
>> not be described in MCFG. It takes the _HID&segment to look for and outputs
>> the RC address resource. Use PNP0C02 devices to describe such RC address
>> resource. Use _UID to match segment to tell which root bus the PNP0C02
>> resource belong to.
>>
>> Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
>> Signed-off-by: Tomasz Nowicki <tn@semihalf.com>
>> ---
>> drivers/pci/pci-acpi.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++
>> drivers/pci/pci.h | 4 +++
>> 2 files changed, 75 insertions(+)
>>
>> diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
>> index d966d47..3557e3a 100644
>> --- a/drivers/pci/pci-acpi.c
>> +++ b/drivers/pci/pci-acpi.c
>> @@ -29,6 +29,77 @@
>> 0x91, 0x17, 0xea, 0x4d, 0x19, 0xc3, 0x43, 0x4d
>> };
>>
>> +#ifdef CONFIG_ARM64
>> +static int acpi_get_rc_addr(struct acpi_device *adev, struct resource *res)
>
> Why can't it return a resource pointer?
Yes, it can return a resource pointer.
Good catch. will fix.
>
>> +{
>> + struct resource_entry *entry;
>> + struct list_head list;
>> + unsigned long flags;
>> + int ret;
>> +
>> + INIT_LIST_HEAD(&list);
>> + flags = IORESOURCE_MEM;
>> + ret = acpi_dev_get_resources(adev, &list,
>> + acpi_dev_filter_resource_type_cb,
>> + (void *) flags);
>> + if (ret < 0) {
>> + dev_err(&adev->dev,
>
> The dev_err() log level is quite excessive here IMO. Why is the
> message useful to users at all? IOW, what is the user supposed to do
> if this message is present in the log?
Ok, this is not really needed, I will delete it.
>
>> + "failed to parse _CRS method, error code %d\n", ret);
>> + return ret;
>> + } else if (ret == 0) {
>> + dev_err(&adev->dev,
>> + "no IO and memory resources present in _CRS\n");
>
> Same here.
will delete.
>
>> + return -EINVAL;
>> + }
>> +
>> + entry = list_first_entry(&list, struct resource_entry, node);
>> + *res = *entry->res;
>> + acpi_dev_free_resource_list(&list);
>> + return 0;
>> +}
>> +
>> +static acpi_status acpi_match_rc(acpi_handle handle, u32 lvl, void *context,
>> + void **retval)
>> +{
>> + u16 *segment = context;
>> + unsigned long long uid;
>> + acpi_status status;
>> +
>> + status = acpi_evaluate_integer(handle, "_UID", NULL, &uid);
>> + if (ACPI_FAILURE(status) || uid != *segment)
>> + return AE_CTRL_DEPTH;
>> +
>> + *(acpi_handle *)retval = handle;
>> + return AE_CTRL_TERMINATE;
>> +}
>> +
>
> Please add a kerneldoc comment describing acpi_get_rc_resources().
OK, will do.
>
>> +int acpi_get_rc_resources(const char *hid, u16 segment, struct resource *res)
>> +{
>> + struct acpi_device *adev;
>> + acpi_status status;
>> + acpi_handle handle;
>> + int ret;
>> +
>> + status = acpi_get_devices(hid, acpi_match_rc, &segment, &handle);
>> + if (ACPI_FAILURE(status)) {
>> + pr_err("Can't find _HID %s device", hid);
>
> Same here.
will delete
>
>> + return -ENODEV;
>> + }
>> +
>> + ret = acpi_bus_get_device(handle, &adev);
>> + if (ret)
>> + return ret;
>> +
>> + ret = acpi_get_rc_addr(adev, res);
>> + if (ret) {
>> + dev_err(&adev->dev, "can't get RC resource");
>
> Same here.
will delete
>
>> + return ret;
>> + }
>> +
>> + return 0;
>> +}
>
> It looks like this function could return the resource pointer just
> fine. What's the problem with that?
It is ok to return the resource pointer, will fix it.
>
>> +#endif
>> +
>> phys_addr_t acpi_pci_root_get_mcfg_addr(acpi_handle handle)
>> {
>> acpi_status status = AE_NOT_EXIST;
>> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
>> index 4518562..17ffa38 100644
>> --- a/drivers/pci/pci.h
>> +++ b/drivers/pci/pci.h
>> @@ -356,4 +356,8 @@ static inline int pci_dev_specific_reset(struct pci_dev *dev, int probe)
>> }
>> #endif
>>
>> +#ifdef CONFIG_ARM64
>> +int acpi_get_rc_resources(const char *hid, u16 segment, struct resource *res);
>> +#endif
>
> Doesn't that depend on ACPI too?
Yes, that depends on ACPI too.
will fix.
Thanks
Dongdong.
>
>> +
>> #endif /* DRIVERS_PCI_H */
>> --
>
> Thanks,
> Rafael
>
> .
>
next prev parent reply other threads:[~2016-11-21 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 9:22 [PATCH V5 0/2] Add ACPI support for HiSilicon SoCs Host Controllers Dongdong Liu
2016-11-18 9:22 ` [PATCH V5 1/2] PCI/ACPI: Provide acpi_get_rc_resources() for ARM64 platform Dongdong Liu
2016-11-18 22:00 ` Rafael J. Wysocki
2016-11-21 8:19 ` Dongdong Liu [this message]
2016-11-18 9:22 ` [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Dongdong Liu
2016-11-18 17:08 ` Bjorn Helgaas
2016-11-21 9:09 ` Gabriele Paoloni
2016-11-21 22:31 ` Bjorn Helgaas
2016-11-22 7:43 ` Gabriele Paoloni
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=41b92e95-7dcd-dbc5-8163-bac8cd3fb441@huawei.com \
--to=liudongdong3@huawei.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=charles.chenxin@huawei.com \
--cc=gabriele.paoloni@huawei.com \
--cc=hanjun.guo@linaro.org \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=pratyush.anand@gmail.com \
--cc=rafael@kernel.org \
--cc=tn@semihalf.com \
--cc=wangzhou1@hisilicon.com \
/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
Powered by JetHome