All of lore.kernel.org
 help / color / mirror / Atom feed
* Where do I put my new driver?
@ 2022-08-08 18:20 Alec Matthews
  2022-09-21 22:26 ` jim.cromie
  0 siblings, 1 reply; 3+ messages in thread
From: Alec Matthews @ 2022-08-08 18:20 UTC (permalink / raw)
  To: kernelnewbies

I've created a new device driver that is responsible for controlling a
GPIO expander. This driver contains gpio_chip code, pinmux/pinconf,
code, pwm, and irq handlers. 

I'm not certain what I should name this driver. `pinctrl-*`, `gpio-*`,
or something else? 

I'm also not sure where this driver belongs in the source tree. Should
it exist in drivers/gpio, drivers/pinctrl, or drivers/pwm?

I have developed this driver out of tree, now I am trying to move it in
tree so I can begin the patch process. I appreciate any insight that
this list may have on where it belongs.


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Where do I put my new driver?
  2022-08-08 18:20 Where do I put my new driver? Alec Matthews
@ 2022-09-21 22:26 ` jim.cromie
  2022-09-22  7:31   ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: jim.cromie @ 2022-09-21 22:26 UTC (permalink / raw)
  To: me; +Cc: kernelnewbies

On Mon, Aug 8, 2022 at 12:21 PM Alec Matthews <me@alecmatthews.dev> wrote:
>
> I've created a new device driver that is responsible for controlling a
> GPIO expander. This driver contains gpio_chip code, pinmux/pinconf,
> code, pwm, and irq handlers.
>
> I'm not certain what I should name this driver. `pinctrl-*`, `gpio-*`,
> or something else?
>

that suggests that you have several different drivers.
each under their own tree to get the same "place"
as the ones already there, that build cleanly,
use the subsystem support, and work.

> I'm also not sure where this driver belongs in the source tree. Should
> it exist in drivers/gpio, drivers/pinctrl, or drivers/pwm?
>
> I have developed this driver out of tree, now I am trying to move it in
> tree so I can begin the patch process. I appreciate any insight that
> this list may have on where it belongs.
>

the path of least resistance might be to just put it in staging.
Once its there and building, thats a milestone.
then when it "works" there, thats clearly another.
then maybe break it up into several ko's if feedback says.

>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Where do I put my new driver?
  2022-09-21 22:26 ` jim.cromie
@ 2022-09-22  7:31   ` Greg KH
  0 siblings, 0 replies; 3+ messages in thread
From: Greg KH @ 2022-09-22  7:31 UTC (permalink / raw)
  To: jim.cromie; +Cc: me, kernelnewbies

On Wed, Sep 21, 2022 at 04:26:29PM -0600, jim.cromie@gmail.com wrote:
> the path of least resistance might be to just put it in staging.

drivers/staging/ is not a dumping ground for drivers under active
development.  Just take the time and get it merged properly in the first
place, it's always faster and simpler that way.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-22  7:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-08 18:20 Where do I put my new driver? Alec Matthews
2022-09-21 22:26 ` jim.cromie
2022-09-22  7:31   ` Greg KH

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.