kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* Adding compatible string to standard UART
@ 2023-08-29 16:58 Ayush Singh
  2023-09-14  7:10 ` Ahmad Fatoum
  0 siblings, 1 reply; 2+ messages in thread
From: Ayush Singh @ 2023-08-29 16:58 UTC (permalink / raw)
  To: kernelnewbies

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

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

* Re: Adding compatible string to standard UART
  2023-08-29 16:58 Adding compatible string to standard UART Ayush Singh
@ 2023-09-14  7:10 ` Ahmad Fatoum
  0 siblings, 0 replies; 2+ messages in thread
From: Ahmad Fatoum @ 2023-09-14  7:10 UTC (permalink / raw)
  To: Ayush Singh, kernelnewbies

Hello Ayush,

On 29.08.23 18:58, Ayush Singh wrote:
> 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?

I haven't checked your links, but from your description, serdev might be what
you're after. In the DT that would be a child node of the existing serial
device.

> 2. Is there some naming convention? I was thinking of `beagle,cc1352-uart`

Not sure about the uart suffix. beagle,play-cc1352 sounds fine for a v1, I think.

> 
> 3. Do I need a documentation entry at `Documentation/devicetree/bindings`? If yes, should it go under serial?

Only if the cc1352 is itself a UART adapter, which doesn't appear to be the case.
Look what the function of the device has and choose the appropriate directory.
For coprocessors that have multiple functions, the main node is described
in mfd/ and the different functions in their respective directories.

> 
> 4. I think I am supposed to use YAML now and not txt?

Yes.

> 
> 5. What are the required fields in this doc file?

Just take a similar device as a template. See what's already in mfd/
and see what's similar to your usage.

Cheers,
Ahmad

> 
> 
> 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
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


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

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

end of thread, other threads:[~2023-09-14  7:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-29 16:58 Adding compatible string to standard UART Ayush Singh
2023-09-14  7:10 ` Ahmad Fatoum

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 NNTP newsgroup(s).