Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753264Ab1EINMG (ORCPT ); Mon, 9 May 2011 09:12:06 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:47407 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752802Ab1EINME (ORCPT ); Mon, 9 May 2011 09:12:04 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=oQRctujoN+T8aypOQf+XuOnTbSKooMGB1GkhZV2vbxeFx4DM7hD6xPSvUktDHrup18 haqKP4XMnwMIeU/10+uMvEifZEGLpSpl0/hG8qkStfVbTc3nYUVAVab9MGtW9RbcqJpx rXxwn7q0bd3L6hV16R5zM9JcYwnUdhLZeLIA8= Subject: Re: [PATCH 4/4] USB: TWL6025 allow different regulator name From: Liam Girdwood To: balbi@ti.com Cc: Graeme Gregory , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, sameo@linux.intel.com, broonie@opensource.wolfsonmicro.com In-Reply-To: <20110509121600.GK1254@legolas.emea.dhcp.ti.com> References: <1303897191-14792-1-git-send-email-gg@slimlogic.co.uk> <1303897191-14792-5-git-send-email-gg@slimlogic.co.uk> <20110427104542.GZ13227@legolas.emea.dhcp.ti.com> <1304867317.3246.10.camel@odin> <20110509090335.GC1254@legolas.emea.dhcp.ti.com> <1304941430.3192.4.camel@odin> <20110509121600.GK1254@legolas.emea.dhcp.ti.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 09 May 2011 14:11:59 +0100 Message-ID: <1304946719.3192.10.camel@odin> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2555 Lines: 59 On Mon, 2011-05-09 at 15:16 +0300, Felipe Balbi wrote: > Hi, > > On Mon, May 09, 2011 at 12:43:49PM +0100, Liam Girdwood wrote: > > On Mon, 2011-05-09 at 12:03 +0300, Felipe Balbi wrote: > > > Hi, > > > > > > On Sun, May 08, 2011 at 04:08:37PM +0100, Liam Girdwood wrote: > > > > On Wed, 2011-04-27 at 13:45 +0300, Felipe Balbi wrote: > > > > > Hi, > > > > > > > > > > On Wed, Apr 27, 2011 at 10:39:51AM +0100, Graeme Gregory wrote: > > > > > > The twl6025 uses a different regulator for USB than the 6030 so select > > > > > > the correct regulator name depending on the subclass of device. > > > > > > > > > > > > Signed-off-by: Graeme Gregory > > > > > > > > > > I don't see the point of this patch. It's just a string. Use the same > > > > > name and add a comment saying that on datasheet/TRM/documentation the > > > > > name LDO is actually referred to as LDOUSB. It's the same functionality > > > > > anyway. > > > > > > > > > > > > > I think for the avoidance of any doubt, it's probably best to use the > > > > TWL6025 string name here as it will importantly match the TWL6025 TRM > > > > and any schematics using the TWL6025. Getting this wrong during TWL6025 > > > > board integration has the potential for hardware damage. > > > > > > I would rather have something that doesn't depend on a correct string > > > and matches based on the device pointer instead. I agree that having the > > > correct string makes it easier to reference schematics/trm and the like, > > > but making the SW depend on the correct spelling of a simple string, is > > > too much for me :-( > > > > > > Specially when getting it wrong "has the potential for hardware damage" > > > :-) > > > > > > > I think it's the lesser evil though, especially for device integrators. > > They will just match the regulator name from the schematics together > > with the TRM name when creating their regulator constraints and having > > different names here will definitely cause confusion. > > Any chance Device Tree could be used to pass that data to kernel > instead, together with regulator names and all needed data for each one > of them ? > Yes, I think this should be the long term aim, but atm we will have to stick with current implementation until regulator has device tree support. Liam -- 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/