All of lore.kernel.org
 help / color / mirror / Atom feed
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: Query on pinctrl usage for DT nodes
Date: Tue, 16 Apr 2013 09:18:22 +0200	[thread overview]
Message-ID: <516CFB3E.8040703@ti.com> (raw)
In-Reply-To: <516C2D74.2090106@wwwdotorg.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 = <X>;

For sure we need to check here as well for overlaps in the bitfields...

-- 
P?ter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Tony Lindgren <tony@atomide.com>,
	device-tree <devicetree-discuss@lists.ozlabs.org>,
	Stephen Warren <swarren@nvidia.com>,
	LAK <linux-arm-kernel@lists.infradead.org>
Subject: Re: Query on pinctrl usage for DT nodes
Date: Tue, 16 Apr 2013 09:18:22 +0200	[thread overview]
Message-ID: <516CFB3E.8040703@ti.com> (raw)
In-Reply-To: <516C2D74.2090106@wwwdotorg.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 = <X>;

For sure we need to check here as well for overlaps in the bitfields...

-- 
Péter

  reply	other threads:[~2013-04-16  7:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  9:16 Query on pinctrl usage for DT nodes Prabhakar Lad
2013-04-03  9:16 ` Prabhakar Lad
2013-04-03 16:44 ` Stephen Warren
2013-04-03 16:44   ` Stephen Warren
2013-04-03 18:38   ` Tony Lindgren
2013-04-03 18:38     ` Tony Lindgren
2013-04-03 18:42     ` Tony Lindgren
2013-04-03 18:42       ` Tony Lindgren
2013-04-15  8:19       ` Peter Ujfalusi
2013-04-15  8:19         ` Peter Ujfalusi
2013-04-15 16:40         ` Stephen Warren
2013-04-15 16:40           ` Stephen Warren
2013-04-16  7:18           ` Peter Ujfalusi [this message]
2013-04-16  7:18             ` Peter Ujfalusi
2013-04-08 13:12   ` Prabhakar Lad
2013-04-08 13:12     ` Prabhakar Lad
2013-04-08 17:24     ` Stephen Warren
2013-04-08 17:24       ` Stephen Warren
2013-04-10  8:12       ` Prabhakar Lad
2013-04-10  8:12         ` Prabhakar Lad
2013-04-10 17:32         ` Stephen Warren
2013-04-10 17:32           ` Stephen Warren
2013-04-10 20:34           ` Tony Lindgren
2013-04-10 20:34             ` Tony Lindgren
2013-04-15  5:09             ` Prabhakar Lad
2013-04-15  5:09               ` Prabhakar Lad
2013-04-15  6:42               ` Prabhakar Lad
2013-04-15  6:42                 ` Prabhakar Lad
2013-04-15  8:26             ` Peter Ujfalusi
2013-04-15  8:26               ` Peter Ujfalusi
2013-04-16 21:32               ` Tony Lindgren
2013-04-16 21:32                 ` Tony Lindgren
2013-04-23  7:42                 ` Peter Ujfalusi
2013-04-23  7:42                   ` Peter Ujfalusi
2013-04-23 18:17                   ` Tony Lindgren
2013-04-23 18:17                     ` Tony Lindgren
2013-05-21 14:16                     ` Manjunathappa, Prakash
2013-05-21 14:16                       ` Manjunathappa, Prakash

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=516CFB3E.8040703@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.