Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932518AbbFFNKU (ORCPT ); Sat, 6 Jun 2015 09:10:20 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:50946 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932413AbbFFNKM (ORCPT ); Sat, 6 Jun 2015 09:10:12 -0400 Date: Sat, 6 Jun 2015 15:10:09 +0200 From: Pavel Machek To: NeilBrown Cc: Kishon Vijay Abraham I , NeilBrown , linux-kernel@vger.kernel.org, GTA04 owners , Tony Lindgren , linux-omap@vger.kernel.org Subject: Re: [PATCH 5/6] phy: twl4030-usb: add support for reading resistor on ID pin. Message-ID: <20150606131009.GD1329@xo-6d-61-c0.localdomain> References: <20150416075945.23307.24424.stgit@notabene.brown> <20150416080304.23307.41913.stgit@notabene.brown> <556C5FF4.3050603@ti.com> <20150602073731.26edbd3b@notabene.brown> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150602073731.26edbd3b@notabene.brown> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1912 Lines: 57 On Tue 2015-06-02 07:37:31, NeilBrown wrote: > On Mon, 1 Jun 2015 19:06:52 +0530 Kishon Vijay Abraham I > wrote: > > > Hi, > > > > On Thursday 16 April 2015 01:33 PM, NeilBrown wrote: > > > From: NeilBrown > > > > > > The twl4030 phy can measure, with low precision, the > > > resistance-to-ground of the ID pin. > > > > > > Add a function to read the value, and export the result > > > via sysfs. > > > > Little sceptical about adding new sysfs entries. Do you have a good reason to > > add this? > > The hardware can report the value, so why not present it to user-space? > > I originally used this with a udev rule which would configure the maximum > current based on the resistance measure - to work with the particular charger > hardware I have. > > More recent patches try to do all of the max-current configuration in the > kernel, so I could live without exporting the value via sysfs if that is a > show-stopper. > > I can't see where the scepticism comes from though. It is a well defined > and cleary documented feature of the hardware. Why not expose it? sysfs interface is supposed to work for different chargers, without userspace noticing. Are these values the ones that are likely to be useful there? > > > + Possible values are: > > > + ground > > > + 102k > > > + 200k > > > + 440k > > > + floating > > > + unknown ...or would it make more sense to export for example numerical ohms, as that's what are other chargers likely to provide? Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/