From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Jones Subject: Re: [PATCH 2/4] mfd: bcm590xx: add support for second i2c slave address space Date: Thu, 17 Apr 2014 07:57:53 +0100 Message-ID: <20140417065753.GC28725@lee--X1> References: <1397501428-8857-1-git-send-email-mporter@linaro.org> <1397501428-8857-3-git-send-email-mporter@linaro.org> <20140416110603.GA19671@lee--X1> <20140416213141.GD12304@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20140416213141.GD12304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Brown Cc: Matt Porter , Devicetree List , Samuel Ortiz , Liam Girdwood , Tim Kryger , Markus Mayer , Linux Kernel Mailing List , Linux ARM Kernel List List-Id: devicetree@vger.kernel.org > > s/regmap/Regmap >=20 > It's consistently written regmap in all the documentation and so on := ) =46urry muff; but the comments still stand for the acronyms. > > addmap{0,1} doesn't quite sit right with me. >=20 > > REVISIT: Ah, it's address-map, rather than add map. Okay, not as ba= d > > as I first thought, but still, is there a better naming convention = you > > could use? >=20 > addrmap or something? Right, that was what I was thinking. However, I prefer something along the lines of 'i2c' and 'i2c_sec' or 'client' and 'client_slv' etc. --=20 Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org =E2=94=82 Open source software for ARM SoCs =46ollow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html