public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: max.schwarz@online.de (Max Schwarz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] pinctrl-rockchip: Change wrong initial assumptions
Date: Wed, 07 May 2014 12:04:36 +0200	[thread overview]
Message-ID: <4611044.dLc2GHPYxV@xq-nb> (raw)
In-Reply-To: <11862890.WUjscWaP3U@diego>

Am Montag, 5. Mai 2014, 13:57:31 schrieb Heiko St?bner:
> Initially due to lack of documentation and (personal) understanding
> I assumed that the area holding the iomux settings would be separate
> from everything else, while in fact the grf registers contain not only
> pinctrl stuff but also dma, usb-phy and general soc-status settings.
> Also things like drive-strength we do not support currently are intermixed.
> 
> The same is true for the pmu, which does not only contain power domains
> but also the system reset as well as well as general registers surviving
> system-resets. Additionally the rk3188 moved parts of the pull-setting
> registers into the pmu space.
> 
> While this wasn't a problem until now, the upcoming rk3288 introduces
> additional changes to both the grf and pmu areas. On it even part of
> the pinmux registers move into the pmu space.
> 
> The code in it's current form supports both the old as well as the
> changed bindings.
> 
> As stated in the v1 thread, this is also a first step to deprecate the
> wrongly included gpio-controllers which now duplicate the recently added
> gpio-dwapb, that should be used instead.
> 
> 
> changes since v1:
> - add select MFD_SYSCON as suggested by Max
> 
> Heiko Stuebner (8):
>   pinctrl: rockchip: do not require 2nd register area
>   pinctrl: rockchip: use regmaps instead of raw mappings
>   pinctrl: rockchip: rockchip_pinctrl in rockchip_get_bank_data
>   pinctrl: rockchip: let pmu registers be supplied by a syscon
>   pinctrl: rockchip: only map bank0-pull-region when pmu regmap missing
>   pinctrl: rockchip: base regmap supplied by a syscon
>   dt-bindings: adapt rockchip-pinctrl doc to changed bindings
>   ARM: dts: rockchip: convert pinctrl nodes to new bindings
> 
>  .../bindings/pinctrl/rockchip,pinctrl.txt          |  28 +++-
>  arch/arm/boot/dts/rk3066a.dtsi                     |   2 +-
>  arch/arm/boot/dts/rk3188.dtsi                      |   9 +-
>  arch/arm/boot/dts/rk3xxx.dtsi                      |   9 +-
>  drivers/pinctrl/Kconfig                            |   1 +
>  drivers/pinctrl/pinctrl-rockchip.c                 | 178
> +++++++++++++++------ 6 files changed, 165 insertions(+), 62 deletions(-)

This series
Acked-by: Max Schwarz <max.schwarz@online.de>

Cheers,
  Max

  parent reply	other threads:[~2014-05-07 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 11:57 [PATCH v2 0/8] pinctrl-rockchip: Change wrong initial assumptions Heiko Stübner
2014-05-05 11:58 ` [PATCH v2 1/8] pinctrl: rockchip: do not require 2nd register area Heiko Stübner
2014-05-05 11:58 ` [PATCH v2 2/8] pinctrl: rockchip: use regmaps instead of raw mappings Heiko Stübner
2014-05-05 11:58 ` [PATCH v2 3/8] pinctrl: rockchip: rockchip_pinctrl in rockchip_get_bank_data Heiko Stübner
2014-05-05 11:59 ` [PATCH v2 4/8] pinctrl: rockchip: let pmu registers be supplied by a syscon Heiko Stübner
2014-05-05 11:59 ` [PATCH v2 5/8] pinctrl: rockchip: only map bank0-pull-region when pmu regmap missing Heiko Stübner
2014-05-05 11:59 ` [PATCH v2 6/8] pinctrl: rockchip: base regmap supplied by a syscon Heiko Stübner
2014-05-05 12:00 ` [PATCH v2 7/8] dt-bindings: adapt rockchip-pinctrl doc to changed bindings Heiko Stübner
2014-05-05 12:00 ` [PATCH v2 8/8] ARM: dts: rockchip: convert pinctrl nodes to new bindings Heiko Stübner
2014-05-09  9:18   ` Linus Walleij
2014-05-07 10:04 ` Max Schwarz [this message]
2014-05-09  9:19 ` [PATCH v2 0/8] pinctrl-rockchip: Change wrong initial assumptions Linus Walleij

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=4611044.dLc2GHPYxV@xq-nb \
    --to=max.schwarz@online.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