[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1455705412.7626.18.camel@suse.com>
Date: Wed, 17 Feb 2016 11:36:52 +0100
From: Oliver Neukum <oneukum@...e.com>
To: Felipe Balbi <balbif@...il.com>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Felipe Balbi <balbi@...nel.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Greg KH <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 2/3] usb: type-c: USB Type-C Connector System Software
Interface
On Wed, 2016-02-17 at 12:29 +0200, Felipe Balbi wrote:
> Hi,
>
> Oliver Neukum <oneukum@...e.com> writes:
> > On Wed, 2016-02-17 at 09:58 +0200, Heikki Krogerus wrote:
> >> On Tue, Feb 16, 2016 at 02:39:47PM +0100, Oliver Neukum wrote:
> >> > Yes, but we need an API. We can't keep adding to it. So if that
> >> > is to be supported, it needs to be defined now.
> >>
> >> When you say API, do you mean the API the class provides to the
> >> drivers? Or did you mean ABI which would be the sysfs in this case?
> >
> > The API to user space. That is the point. We cannot break user space.
> > Once this sysfs API is upstream we are stuck with it.
>
> yeah, in fact I have been wondering if sysfs is the best interface to
That is the discussion we must have.
> userspace. I talked with Heikki a few days back about this; I was
> wondering if something like what the NFC folks did with netlink would be
> better here.
I doubt that, because the main user is likely to be udev scripts.
They can easily deal with sysfs attributes.
Regards
Oliver
Powered by blists - more mailing lists