Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752214AbbEZT1i (ORCPT ); Tue, 26 May 2015 15:27:38 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:33459 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752049AbbEZT1c (ORCPT ); Tue, 26 May 2015 15:27:32 -0400 Date: Tue, 26 May 2015 21:27:07 +0200 From: Andreas Werner To: Felipe Balbi Cc: linux-kernel@vger.kernel.org Subject: Re: regmap different register size Message-ID: <20150526192707.GA28895@wernerandy.de> References: <20150526185425.GA26217@wernerandy.de> <20150526190039.GX26599@saruman.tx.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150526190039.GX26599@saruman.tx.rr.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1076 Lines: 28 On Tue, May 26, 2015 at 02:00:39PM -0500, Felipe Balbi wrote: > Hi, > > On Tue, May 26, 2015 at 08:54:25PM +0200, Andreas Werner wrote: > > i have a question regarding regmap usage. > > > > I have a i2c multifunction device which does have a register and value > > width of 8bits except the revision register. The revision can only be > > read by a i2c block transfer. > > read revision during probe using i2c block transfer, cache the value in > your own driver structure and all subsequent reads just return the > cached value. Everything else should be ok via regmap. This is first > thing that came to mind, maybe there's a better way. > > -- > balbi This is what I want to do yes and i think this would be the only way to do it because there is no mechanism to handle different register sizes with regmap. Regards Andy -- 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/