From mboxrd@z Thu Jan 1 00:00:00 1970 From: peter.ujfalusi@ti.com (Peter Ujfalusi) Date: Tue, 16 Apr 2013 09:18:22 +0200 Subject: Query on pinctrl usage for DT nodes In-Reply-To: <516C2D74.2090106@wwwdotorg.org> References: <515C5C76.3080009@wwwdotorg.org> <20130403183803.GA10155@atomide.com> <20130403184202.GB10155@atomide.com> <516BB818.3060603@ti.com> <516C2D74.2090106@wwwdotorg.org> Message-ID: <516CFB3E.8040703@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/15/2013 06:40 PM, Stephen Warren wrote: > So, the solution here is for pinctrl-single to create a separate > pin/group object for each separately controllable entity, and that may > be each bit in a register rather than each register, depending on HW. Exactly what I was thinking. It would be ideal if we could do this dynamically, so when a new pinctr-single,bits is added we create a new object (after checking for overlapping bits from previous objects). If this is not possible we should have new property telling pinctrl-single how many objects to create for one physical register (used only when pinctrl-single,bit-per-mux is defined), something like: pinctrl-single,bit-per-mux; pinctrl-single,functions-per-register = ; For sure we need to check here as well for overlaps in the bitfields... -- P?ter From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Ujfalusi Subject: Re: Query on pinctrl usage for DT nodes Date: Tue, 16 Apr 2013 09:18:22 +0200 Message-ID: <516CFB3E.8040703@ti.com> References: <515C5C76.3080009@wwwdotorg.org> <20130403183803.GA10155@atomide.com> <20130403184202.GB10155@atomide.com> <516BB818.3060603@ti.com> <516C2D74.2090106@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <516C2D74.2090106@wwwdotorg.org> 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: Stephen Warren Cc: Tony Lindgren , device-tree , Stephen Warren , LAK List-Id: devicetree@vger.kernel.org On 04/15/2013 06:40 PM, Stephen Warren wrote: > So, the solution here is for pinctrl-single to create a separate > pin/group object for each separately controllable entity, and that may > be each bit in a register rather than each register, depending on HW. Exactly what I was thinking. It would be ideal if we could do this dynamically, so when a new pinctr-single,bits is added we create a new object (after checking for overlapping bits from previous objects). If this is not possible we should have new property telling pinctrl-single = how many objects to create for one physical register (used only when pinctrl-single,bit-per-mux is defined), something like: pinctrl-single,bit-per-mux; pinctrl-single,functions-per-register =3D ; For sure we need to check here as well for overlaps in the bitfields... -- = P=E9ter