Thread (32 messages) 32 messages, 5 authors, 2018-02-16

Re: [PATCH v13 7/9] ACPI: Translate the I/O range of non-MMIO devices before scanning

From: Andy Shevchenko <hidden>
Date: 2018-02-14 16:17:00
Also in: linux-acpi, linux-arch, linux-pci, lkml

On Wed, Feb 14, 2018 at 5:33 PM, John Garry [off-list ref] wrote:
On 14/02/2018 13:53, Andy Shevchenko wrote:
quoted
On Tue, Feb 13, 2018 at 7:45 PM, John Garry [off-list ref] wrote:
quoted
quoted
+       sys_port = logic_pio_trans_hwaddr(&host->fwnode, res->start,
len);
+       if (sys_port == -1UL)
quoted
Wouldn't it be better to compare with ULONG_MAX?
Could do, being the same thing. Maybe people prefer -1UL as it saves having
to figure out what ULONG_MAX is :)
-1UL looks confusing.

Another approach is to use ~0UL if that is preferable.
quoted
quoted
+       list_for_each_entry(rentry, &resource_list, node)
+               resources[count++] = *rentry->res;
quoted
It has similarities with acpi_create_platform_device().
I guess we can utilize existing code.
For sure, this particular segment is effectively same as part of
acpi_create_platform_device():
Not the same, acpi_create_platform_device() does a bit more than
copying the resources. If it indeed makes no hurt...
        list_for_each_entry(rentry, &resource_list, node)
            acpi_platform_fill_resource(adev, rentry->res,
                            &resources[count++]);
So is your idea to refactor this common segment into a helper function?
...I would go with helper.
quoted
quoted
+               char *name = &acpi_indirect_io_mfd_cell[count].name[0];
+               char *pnpid = &acpi_indirect_io_mfd_cell[count].pnpid[0];

Plain x is equivalent to &x[0].
Right, but I thought for arrays that we should use address of x rather than
x itself, no?
x is addressed by it's beginning.

-- 
With Best Regards,
Andy Shevchenko
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help