[lkml]   [2018]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v5 1/6] fieldbus_dev: add Fieldbus Device subsystem.
On Wed, Dec 5, 2018 at 11:32 PM Sven Van Asbroeck <> wrote:
> On Wed, Dec 5, 2018 at 2:17 PM Greg KH <> wrote:
> >
> > Great, then call it a 'fieldbus' class, not "fieldbus_dev' class.
> Small nit:
> Hardware connected to a fieldbus comes in two distinct flavours:
> - clients (e.g. thermometer, robotic arm) called "fieldbus devices"
> - servers (e.g. a PLC) called "fieldbus controllers"
> Their userspace APIs will probably differ quite a lot.
> The userspace API created by the patch is only for clients a.k.a.
> "fieldbus devices". That's why I'm writing 'fieldbus_dev' all over the place.
> For simplicity, we could change that to just 'fieldbus'. But would this get
> us in trouble when, at some point, we want to add a userspace API for
> servers a.k.a. "fieldbus controllers" ?

In the long run, would you expect to support more devices or more
controllers that need a distinct driver? Whichever we have more of should
probably get the shorter name.


 \ /
  Last update: 2018-12-05 23:52    [W:0.061 / U:0.504 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site