linux-kernel - Re: [PATCH 2/3] usb: type-c: USB Type-C Connector System Software Interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Feb 2016 15:34:19 +0200
From:	Felipe Balbi <balbi@...nel.org>
To:	Oliver Neukum <oneukum@...e.com>, Felipe Balbi <balbif@...il.com>
Cc:	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	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


Hi,

Oliver Neukum <oneukum@...e.com> writes:
>> > 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.

I'm entirely sure about this. I think it's not too far-fetched to think
that, eventually, we will need an actual stack exposed for the CC pin.

> They can easily deal with sysfs attributes.

right

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)