From: Ayush Singh <ayushdevel1325@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Adding compatible string to standard UART
Date: Tue, 29 Aug 2023 22:28:46 +0530 [thread overview]
Message-ID: <1e8badf8-dfea-bd37-ab1d-c8d8f9de6f9b@gmail.com> (raw)
Hello everyone. I have been working on submitting my GSoC23 driver [1]
to be merged upstream.
BeaglePlay has a specific UART that is connected to the CC1352
Co-processor. This UART is used to communicate with CC1352 co-processor.
It is also used to flash stuff to this co-processor using bsl. Thus, it
should be possible to disable it with an overlay and show it as a normal
ttyS* device. Currently, the beagle kernel uses the following dts [3].
My driver uses this UART and thus I need to patch the devicetree.
However, I am not too sure what I need to do to submit my device tree
patch upstream. I read the Submitting Devicetree (DT) binding patches'
doc [2], but I don't understand a few things:
1. Should I even be using device tree? Maybe there is a better method?
2. Is there some naming convention? I was thinking of `beagle,cc1352-uart`
3. Do I need a documentation entry at
`Documentation/devicetree/bindings`? If yes, should it go under serial?
4. I think I am supposed to use YAML now and not txt?
5. What are the required fields in this doc file?
Ayush Singh
[1]: https://github.com/Ayush1325/linux/tree/gb-beagleplay
[2]: https://docs.kernel.org/devicetree/bindings/submitting-patches.html
[3]:
https://git.beagleboard.org/beagleboard/linux/-/blob/v5.10.168-ti-arm64-r103/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts#L1206
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2023-08-29 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:58 Ayush Singh [this message]
2023-09-14 7:10 ` Adding compatible string to standard UART Ahmad Fatoum
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=1e8badf8-dfea-bd37-ab1d-c8d8f9de6f9b@gmail.com \
--to=ayushdevel1325@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).