From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Ujfalusi Subject: Re: Query on pinctrl usage for DT nodes Date: Mon, 15 Apr 2013 10:26:07 +0200 Message-ID: <516BB99F.2080502@ti.com> References: <515C5C76.3080009@wwwdotorg.org> <5162FD4A.1030909@wwwdotorg.org> <5165A22B.4070200@wwwdotorg.org> <20130410203408.GP10155@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20130410203408.GP10155@atomide.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Tony Lindgren Cc: Stephen Warren , Stephen Warren , device-tree , Prabhakar Lad , linus.walleij@linaro.org, LAK List-Id: devicetree@vger.kernel.org On 04/10/2013 10:34 PM, Tony Lindgren wrote: > Yeah how about just change the pintctrl-single,bits register > naming to be register + bit? Something like 0xdeadbeef.0 and > 0xdeadbeef.1 and so on. Something like this might work I think. It is going to be a bit tricky IMHO since we might need span out new 'register' every time a device requests fo= r a new pinctrl-single,bits for already used register in the pinctrl-single,bit-per-mux area. In this way we still can make sure that certain bit are only used by a single driver. -- = P=E9ter