From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Mon, 12 Sep 2011 15:50:47 +0200 Subject: [U-Boot] [PATCH 0/2] misc:max8998 Support for MAX8998 PMIC driver In-Reply-To: <20110912151841.36f49466@lmajewski.digital.local> References: <1314868412-2949-1-git-send-email-l.majewski@samsung.com> <20110912101428.20e2f74f@lmajewski.digital.local> <4E6DE3EF.6080107@denx.de> <20110912151841.36f49466@lmajewski.digital.local> Message-ID: <4E6E0E37.2040804@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 09/12/2011 03:18 PM, Lukasz Majewski wrote: > Hi Stefano, > > Thanks for your reply. Hi Lucasz, >> Maybe getting rid of special manufacturer names as fsl_pmic, >> max_pmic... and using a general access for this kind of chips ? From >> code your patch is not very distant from what we currently have. Any >> opinion about this ? > > Yes, you are right. I've looked to the fsl_pmic driver when I was > preparing patch for MAX8998. I have supposed... > > As you have written, dealing with those two PMICs boils down to > reading/writing their internal registers via I2C by i2c.h API. > > We can think of a common PMIC framework, which is consisting of methods > for reading/writing internal registers, enabling outputs of those > devices. Exactly ! > > PMIC specific data (like register map, I2C addresses) can be stored in > *.h files. Yes, this is what I meant ;-) > > I can prepare some common framework and post proposition on the > mailing list. On the beginning I'll focus on MAX8998 and FSL. Agree. Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================