Devicetree
 help / color / mirror / Atom feed
From: Alex Elder <elder@riscstar.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	arnd@arndb.de, 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:04 -0500	[thread overview]
Message-ID: <d61b2a72-aa24-4119-bf5f-8a2456f6c9b5@riscstar.com> (raw)
In-Reply-To: <2026081455-eternity-douche-900b@gregkh>

On 8/13/26 8:11 PM, Greg KH wrote:
> On Thu, Aug 13, 2026 at 05:29:42PM -0500, Alex Elder wrote:
>> +#define DRIVER_NAME "tc9564-pci"
> 
> What about just using KBUILD_MODNAME?

Yes, I'll use that.  The underscore versus dash doesn't
matter...
> 
>> +static int
>> +tc9564_function_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> 
> But wow, this is a tiny driver, feels odd to have it in misc/ but ok, if
> you think it should be here...

I put it in misc/ because lan966xc_pci.c, which also uses
a pci-ep-bus, is located there.  That driver also calls
of_platform_default_populate(), though it also loads a
DT overlay which isn't needed here.

It is indeed tiny, and your comment makes me think it
could easily become a generic driver (along the lines
of "simple-mfd-i2c.c").  That way other similar future
SoCs could just add their compatible string.

So two questions (for anyone):
- Would that be preferred--rename this to target a generic
   situation?  For example, "static-pci-ep-bus.c"?
- Where should such a driver be located?  For example,
   drivers/misc/, drivers/pci/controller/, or something else?

					-Alex

> thanks,
> 
> greg k-h


  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 [this message]
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
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=d61b2a72-aa24-4119-bf5f-8a2456f6c9b5@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=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