linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pza@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] reset: add the Berlin reset controller driver
Date: Mon, 9 Jun 2014 13:23:11 +0200	[thread overview]
Message-ID: <20140609112311.GA22176@pengutronix.de> (raw)
In-Reply-To: <53958D52.2050402@gmail.com>

Hi Sebastian,

On Mon, Jun 09, 2014 at 12:32:50PM +0200, Sebastian Hesselbarth wrote:
> I currently have no way to look it up myself, but is reset API providing
> a way to deal with phandle+specifier with more than one parameter?

You could provide a custom rcdev->of_xlate callback and encode
multiple phandle args into the reset line "index".

static int of_reset_xlate(struct reset_controller_dev *rcdev,
                          const struct of_phandle_args *reset_spec)
{
	return reset_spec->args[0] * 32 + reset_spec->args[1];
}

> Chip-ctrl has a bunch of other reset bits spread over the regset, having
> the offset encoded in the specifier would save us some SoC specific
> boiler plate, i.e.
> 
> reset = <&chip 0x104 14>;

That should be possible.

regards
Philipp

  reply	other threads:[~2014-06-09 11:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 15:48 [PATCH 0/9] ARM: Berlin: USB support Antoine Ténart
2014-06-05 15:48 ` [PATCH 1/9] reset: add the Berlin reset controller driver Antoine Ténart
2014-06-05 16:36   ` Philipp Zabel
2014-06-05 16:56     ` Antoine Ténart
2014-06-06 10:44     ` Sebastian Hesselbarth
2014-06-09 10:32   ` Sebastian Hesselbarth
2014-06-09 11:23     ` Philipp Zabel [this message]
2014-06-05 15:48 ` [PATCH 2/9] ARM: Berlin: select the reset controller Antoine Ténart
2014-06-05 15:48 ` [PATCH 3/9] ARM: dts: berlin: add a required reset property in the chip controller node Antoine Ténart
2014-06-05 16:39   ` Philipp Zabel
2014-06-05 16:44     ` Antoine Ténart
2014-06-05 15:48 ` [PATCH 4/9] usb: phy: add the Berlin USB PHY driver Antoine Ténart
2014-06-06  6:39   ` Vivek Gautam
2014-06-06  7:11     ` Antoine Ténart
2014-06-06 11:02       ` Vivek Gautam
2014-06-19 13:45         ` Felipe Balbi
2014-06-06 10:54   ` Sebastian Hesselbarth
2014-06-06 11:59     ` Antoine Ténart
2014-06-09  8:26     ` Jisheng Zhang
2014-06-09 10:11       ` Sebastian Hesselbarth
2014-06-09 10:52         ` Alexandre Belloni
2014-06-05 15:48 ` [PATCH 5/9] Documentation: bindings: add doc for the Berlin USB PHY Antoine Ténart
2014-06-05 15:48 ` [PATCH 6/9] usb: chipidea: add Berlin USB support Antoine Ténart
2014-06-06 10:55   ` Sebastian Hesselbarth
2014-06-06 12:01     ` Antoine Ténart
2014-06-05 15:48 ` [PATCH 7/9] Documentation: bindings: add doc for the Berlin ChipIdea USB driver Antoine Ténart
2014-06-05 15:48 ` [PATCH 8/9] ARM: dts: berlin: add BG2Q nodes for USB support Antoine Ténart
2014-06-05 15:48 ` [PATCH 9/9] ARM: dts: Berlin: enable USB on the BG2Q DMP Antoine Ténart
2014-06-09  4:30 ` [PATCH 0/9] ARM: Berlin: USB support Peter Chen
2014-06-09 10:14   ` Sebastian Hesselbarth
2014-06-10  1:16     ` Peter Chen

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=20140609112311.GA22176@pengutronix.de \
    --to=pza@pengutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).