From: Alex Elder <elder@riscstar.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
arnd@arndb.de, gregkh@linuxfoundation.org, bhelgaas@google.com,
daniel@riscstar.com, mohdayaa@qti.qualcomm.com,
lbiancon@qti.qualcomm.com, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] misc: tc9564: introduce base PCI driver
Date: Fri, 14 Aug 2026 11:55:26 -0500 [thread overview]
Message-ID: <d00b4b0f-5958-4c7d-9f80-7fb283ef90e6@riscstar.com> (raw)
In-Reply-To: <20260814-rainbow-alchemical-gaur-9fd8de@quoll>
On 8/14/26 2:03 AM, Krzysztof Kozlowski wrote:
> On Thu, Aug 13, 2026 at 05:29:42PM -0500, Alex Elder wrote:
>> +static struct pci_driver tc9564_function_driver = {
>> + .name = DRIVER_NAME,
>> + .id_table = tc9564_function_id_table,
>> + .probe = tc9564_function_probe,
>> + .remove = tc9564_function_remove,
>> + .driver = {
>> + .name = DRIVER_NAME,
>> + .owner = THIS_MODULE,
>
> You just copied some old driver. Why do you need this?
What do you mean I "just copied some old driver"?
I do now see that a PCI driver doesn't need to set it,
because pci_register_driver() sets it automatically.
I will remove that in the next version.
-Alex>
>> + },
>> +};
>> +module_pci_driver(tc9564_function_driver);
>> +
>> +MODULE_DESCRIPTION("Toshiba TC9564 PCIe Embedded Function Driver");
>> +MODULE_LICENSE("GPL");
>> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
>> index 6501c949c5b76..b484f1b1d0e71 100644
>> --- a/drivers/pci/quirks.c
>> +++ b/drivers/pci/quirks.c
>> @@ -6388,6 +6388,7 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_XILINX, 0x5020, of_pci_make_dev_node);
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_XILINX, 0x5021, of_pci_make_dev_node);
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_REDHAT, 0x0005, of_pci_make_dev_node);
>> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_EFAR, 0x9660, of_pci_make_dev_node);
>> +DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_TOSHIBA, 0x0220, of_pci_make_dev_node);
>>
>> /*
>> * Devices known to require a longer delay before first config space access
>> --
>> 2.53.0
>>
next prev parent reply other threads:[~2026-08-14 16:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 22:29 [PATCH 0/2] PCI: introduce TC9564 misc driver Alex Elder
2026-08-13 22:29 ` [PATCH 1/2] dt-bindings: misc: introduce pci1179,0220.yaml Alex Elder
2026-08-14 1:45 ` sashiko-bot
2026-08-14 16:55 ` Alex Elder
2026-08-14 7:01 ` Krzysztof Kozlowski
2026-08-14 16:55 ` Alex Elder
2026-08-17 6:18 ` Krzysztof Kozlowski
2026-08-20 17:18 ` Alex Elder
2026-08-15 20:46 ` Rob Herring (Arm)
2026-08-20 17:18 ` Alex Elder
2026-08-21 19:10 ` Rob Herring
2026-08-21 22:07 ` Alex Elder
2026-08-17 2:43 ` Rob Herring
2026-08-20 17:22 ` Alex Elder
2026-08-13 22:29 ` [PATCH 2/2] misc: tc9564: introduce base PCI driver Alex Elder
2026-08-14 1:11 ` Greg KH
2026-08-14 7:31 ` Arnd Bergmann
2026-08-14 16:55 ` Alex Elder
2026-08-14 16:55 ` Alex Elder
2026-08-14 1:59 ` sashiko-bot
2026-08-14 16:55 ` Alex Elder
2026-08-14 7:03 ` Krzysztof Kozlowski
2026-08-14 16:55 ` Alex Elder [this message]
2026-08-17 6:15 ` Krzysztof Kozlowski
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=d00b4b0f-5958-4c7d-9f80-7fb283ef90e6@riscstar.com \
--to=elder@riscstar.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=daniel@riscstar.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lbiancon@qti.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mohdayaa@qti.qualcomm.com \
--cc=robh@kernel.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