From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423329AbcBQNyZ (ORCPT ); Wed, 17 Feb 2016 08:54:25 -0500 Received: from mx2.suse.de ([195.135.220.15]:60205 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423150AbcBQNyW (ORCPT ); Wed, 17 Feb 2016 08:54:22 -0500 Message-ID: <1455717104.7626.20.camel@suse.com> Subject: Re: [PATCH 2/3] usb: type-c: USB Type-C Connector System Software Interface From: Oliver Neukum To: Felipe Balbi Cc: balbif@gmail.com, Heikki Krogerus , Mathias Nyman , Greg KH , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Date: Wed, 17 Feb 2016 14:51:44 +0100 In-Reply-To: <87egcbihpg.fsf@ti.com> References: <1455037283-106479-1-git-send-email-heikki.krogerus@linux.intel.com> <1455037283-106479-3-git-send-email-heikki.krogerus@linux.intel.com> <20160209182155.GC31787@kroah.com> <20160210103042.GB5270@kuha.fi.intel.com> <20160210172035.GA28335@kroah.com> <20160211135011.GA32213@kuha.fi.intel.com> <1455550218.22176.11.camel@suse.com> <20160216092238.GA18565@kuha.fi.intel.com> <1455629987.4532.25.camel@suse.com> <20160217075841.GA24649@kuha.fi.intel.com> <1455699834.7626.4.camel@suse.com> <87fuwrsk7w.fsf@ti.com> <1455705412.7626.18.camel@suse.com> <87egcbihpg.fsf@ti.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2016-02-17 at 15:34 +0200, Felipe Balbi wrote: > Hi, > > Oliver Neukum 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 What exactly are you sure about about? > that, eventually, we will need an actual stack exposed for the CC pin. The raw CC pin? What about the timing requirement? Regards Oliver