From: Jacko Dirks <jdirks.linuxdev@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Location of files for a new driver
Date: Tue, 5 May 2020 16:38:06 +0200 [thread overview]
Message-ID: <20200505143806.GA589943@vasteMachine> (raw)
In-Reply-To: <20200505142032.GA793696@kroah.com>
On Tue, May 05, 2020 at 04:20:32PM +0200, Greg KH wrote:
> drivers/staging/ is only for code that needs lots and lots of work to
> get into the "real" part of the kernel. It also requires a TODO file
> that lists what is left to do to get it out of that location.
Oh, I did not know that staging was optional. Well, I will attempt to
skip staging in that case
> It all depends on what you are writing. What exactly does this code do?
> That will determine where it goes in the kernel tree.
The code is a driver for the Broadcom BSC, which lives on the Raspberry
Pi 3 & 4 (at least, maybe also on 1 & 2). This device can act as an I2C
slave. To "announce" the device (tell the device tree which pins need to
be configured how, etcetera) I need to change existing dts/dtsi files,
to actually be able to enable the device I need to create a new overlay.
Finally, the actual driver needs to be created in drivers/i2c/busses. And
then there is also some makefile, documentation and kconfig.
Does that sound right?
> thanks,
No, thank you!
Jacko Dirks
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-05-05 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:58 Location of files for a new driver Jacko Dirks
2020-05-05 14:20 ` Greg KH
2020-05-05 14:38 ` Jacko Dirks [this message]
2020-05-05 18:05 ` Greg KH
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=20200505143806.GA589943@vasteMachine \
--to=jdirks.linuxdev@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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 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.