Thread (37 messages) 37 messages, 8 authors, 2026-01-22

Re: [PATCH v3 02/14] serdev: Add an API to find the serdev controller associated with the devicetree node

From: Bartosz Golaszewski <brgl@kernel.org>
Date: 2026-01-12 10:59:59
Also in: linux-acpi, linux-arm-msm, linux-devicetree, linux-kbuild, linux-pci, linux-pm, linux-serial, lkml, platform-driver-x86

On Mon, 12 Jan 2026 08:55:21 +0100, Manivannan Sadhasivam
[off-list ref] said:
On Mon, Jan 12, 2026 at 09:50:33AM +0200, Andy Shevchenko wrote:
quoted
On Sat, Jan 10, 2026 at 12:26:20PM +0530, Manivannan Sadhasivam via B4 Relay wrote:
quoted
Add of_find_serdev_controller_by_node() API to find the serdev controller
device associated with the devicetree node.
Why OF-centric code? No, please do it fwnode-based.
No issues for me. But the existing APIs in serdev are OF based. If uniformity is
not needed, I can change it to a fwnode based API.
Using fwnodes here shouldn't be an issue, even though serdev core assigns
dev->of_node, it will be converted to dev->fwnode when the device is registered.

Bart
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help