[lkml]   [2018]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH anybus v3 5/6] dt-bindings: anybuss-host: document devicetree binding
Hi Arnd, thank you for the review and the feedback !

> To allow describing connected devices, I think we need a #address-cells
> and #size-cells property here, with fixed values.

I'm not sure I understand. Connected devices aren't described in the
devicetree. The anybus specification defines an id register, which is
then used to load the client driver automatically, in the manner of

In case I have misinterpreted your feedback, could you clarify a bit?

E.g. here's the definition of an anybus client driver, a profinet card:

static struct anybuss_client_driver profinet_driver = {
.probe = profinet_probe,
.remove = profinet_remove,
.driver = {
.name = "hms-profinet",
.owner = THIS_MODULE,
.fieldbus_type = 0x0089,

static int __init profinet_init(void)
return anybuss_client_driver_register(&profinet_driver);

 \ /
  Last update: 2018-11-08 15:22    [W:0.115 / U:2.580 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site