From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932123AbcEXKWP (ORCPT ); Tue, 24 May 2016 06:22:15 -0400 Received: from mx2.suse.de ([195.135.220.15]:56665 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753905AbcEXKWM (ORCPT ); Tue, 24 May 2016 06:22:12 -0400 Message-ID: <1464085118.11721.11.camel@suse.com> Subject: Re: [RFC PATCHv2] usb: USB Type-C Connector Class From: Oliver Neukum To: Heikki Krogerus Cc: Guenter Roeck , Andy Shevchenko , Rajaram R , Felipe Balbi , Mathias Nyman , Greg KH , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Date: Tue, 24 May 2016 12:18:38 +0200 In-Reply-To: <20160524100822.GB26874@kuha.fi.intel.com> References: <1463751447.14070.6.camel@suse.com> <573FF752.2080204@roeck-us.net> <1463813039.24976.9.camel@suse.com> <5741D63E.1050206@roeck-us.net> <1463981641.12181.5.camel@suse.com> <5743053D.5060307@roeck-us.net> <1464011884.12181.59.camel@suse.com> <57431704.3030703@roeck-us.net> <1464018904.12181.62.camel@suse.com> <20160523165212.GA5964@roeck-us.net> <20160524100822.GB26874@kuha.fi.intel.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 Tue, 2016-05-24 at 13:08 +0300, Heikki Krogerus wrote: > Hi Guenter, > > On Mon, May 23, 2016 at 09:52:12AM -0700, Guenter Roeck wrote: > > On Mon, May 23, 2016 at 05:55:04PM +0200, Oliver Neukum wrote: > > > On Mon, 2016-05-23 at 07:43 -0700, Guenter Roeck wrote: > > > > On 05/23/2016 06:58 AM, Oliver Neukum wrote: > > > > > > > > Now I am confused. Are you saying that the choice of Alternate Mode does > > > > > not belong into user space? > > > > > > > > > > > > > No; sorry for the confusion. The above was meant to apply to my use > > > > of "preferred mode", not yours. I was trying to say that the choice of > > > > preferred roles (which determines if Try.SRC or Try.SNK is enabled) > > > > should belong primarily into the kernel, to be determined by the platform > > > > (presumably via ACPI, devicetree data, or platform data). If it should > > > > > > Why on earth? That is most clearly a policy decision. > > > > > > > The question is not that much if it is policy (it is), but if the policy > > should be driven by the platform or by user space. I think there needs > > to be at least a default driven by the platform. As already mentioned, > > I am ok with a means to override this platform default from user space. > > But if user space doesn't say, there still needs to be a default. > > I don't completely agree with that. The platform should not, and > actually in most cases with ACPI AFAIK, will not provide any > "preferences" to the OS about anything. The platform should only > provide the OS the physical capabilities and nothing else. So if for > example the platform is capable of acting as only source with a Type-C > port, that is what it needs to tell to the OS so possibly the PHY can > be programmed accordingly, etc. May I suggest that the point is moot as long as we agree that user space needs to be able to set a policy? The OS cannot ignore the port before user space tells it what to do. So a default will be needed. The OS must act conservatively, which means it cannot deactivate hardware. So if a port can do DRP, that must be the default. I would go so far that I would suggest that we add a module parameter for Try.SRC and Try.SNK to avoid trouble during boot. > So IMO, just like with any decision related to what the system will > ultimately be used for, decision about the preferred role really > belongs to the userspace. Yes, but ought the APIs for role, mode and PD be separate or not. Sorry to sound like a broken record, but you need to provide some higher level planning here. Regards Oliver