Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312019
| From | "liudongdong (C)" <liudongdong3@huawei.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V3 20/21] pci, acpi: Match PCI config space accessors against platfrom specific quirks. |
| Date | 2016-01-19 10:00 +0100 |
| Message-ID | <qSAiS-5me-29@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <qQtES-hT-23@gated-at.bofh.it> <qQSaf-yO-47@gated-at.bofh.it> <qShpT-GJ-5@gated-at.bofh.it> <qStKr-Kn-21@gated-at.bofh.it> <qSzmO-4JC-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
在 2016/1/19 15:55, Tomasz Nowicki 写道:
> On 19.01.2016 02:49, liudongdong (C) wrote:
>> Hi Tomasz, Mark
>>
>> 在 2016/1/18 20:41, Tomasz Nowicki 写道:
>>> On 14.01.2016 16:36, Mark Salter wrote:
>>>>> +extern struct pci_mcfg_fixup __start_acpi_mcfg_fixups[];
>>>>> >+extern struct pci_mcfg_fixup __end_acpi_mcfg_fixups[];
>>>>> >+
>>>>> >+static struct pci_ops *pci_mcfg_check_quirks(struct acpi_pci_root
>>>>> *root)
>>>>> >+{
>>>>> >+ struct pci_mcfg_fixup *f;
>>>>> >+ int bus_num = root->secondary.start;
>>>>> >+ int domain = root->segment;
>>>>> >+
>>>>> >+ /*
>>>>> >+ * First match against PCI topology <domain:bus> then use DMI or
>>>>> >+ * custom match handler.
>>>>> >+ */
>>>>> >+ for (f = __start_acpi_mcfg_fixups; f < __end_acpi_mcfg_fixups;
>>>>> f++) {
>>>>> >+ if ((f->domain == domain || f->domain ==
>>>>> PCI_MCFG_DOMAIN_ANY) &&
>>>>> >+ (f->bus_num == bus_num || f->bus_num ==
>>>>> PCI_MCFG_BUS_ANY) &&
>>>>> >+ (f->system ? dmi_check_system(f->system) : 0 ||
>>>>> >+ f->match ? f->match(f, root) : 0))
>>>>> >+ return f->ops;
>>>> I think this would be better as:
>>>>
>>>> (f->system ? dmi_check_system(f->system) : 1 &&
>>>> f->match ? f->match(f, root) : 1))
>>>> return f->ops;
>>>>
>>>> Otherwise, one has to call dmi_check_system() from f->match() if
>>>> access to root is needed.
>>>
>>
>> Non-DMI, we need not to call dmi_check_system() from f->match(),
>> we can use _HID to decide to hook the pci_ops or not.
>
> Sorry, but I dont understand your point. Can you elaborate?
>
> With Mark modification, you can use the following cases to identify platform:
> 1. DMI only
> 2. f->match() only (_HID can be used there)
> 3. DMI and f->match()
>
> DMI used to be very convenient way to recognise platform, sometimes it is not enough, hence f->match() alternative.
>
Yes, you are right, I was wrong.
In my case, I can use the second point.
2. f->match() only (_HID can be used there)
Thanks
Dongdong
> Tomasz
>
>
>
> .
>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH V3 20/21] pci, acpi: Match PCI config space accessors against platfrom specific quirks. Tomasz Nowicki <tn@semihalf.com> - 2016-01-18 13:50 +0100
Re: [PATCH V3 20/21] pci, acpi: Match PCI config space accessors against platfrom specific quirks. "liudongdong (C)" <liudongdong3@huawei.com> - 2016-01-19 03:00 +0100
Re: [PATCH V3 20/21] pci, acpi: Match PCI config space accessors against platfrom specific quirks. Tomasz Nowicki <tn@semihalf.com> - 2016-01-19 09:00 +0100
Re: [PATCH V3 20/21] pci, acpi: Match PCI config space accessors against platfrom specific quirks. "liudongdong (C)" <liudongdong3@huawei.com> - 2016-01-19 10:00 +0100
csiph-web