linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt
Date: Mon, 10 Jun 2013 15:06:35 +0200	[thread overview]
Message-ID: <201306101506.36098.heiko@sntech.de> (raw)
In-Reply-To: <CACRpkdaV0ipY4mYHt998D=NNKrpDaFhCA949V0-93NkOKcvHyA@mail.gmail.com>

Am Montag, 10. Juni 2013, 14:52:13 schrieb Linus Walleij:
> On Sun, Jun 9, 2013 at 1:59 AM, Heiko St?bner <heiko@sntech.de> wrote:
> > following your suggestions for a common handling of things like pulls in
> > dt, I've come up with the following solution - hopefully I've gotten the
> > correct meaning of your explanaitions.
> > 
> > It handles all the pinconfigs that either ignore the argument, or have
> > very simple one, like PIN_CONFIG_OUTPUT does.
> 
> OK patches applied. It needs some rough fixes like NULL check
> on kmalloc() but it'll do for a starter.

gah, sorry ... I have urge to crawl under a rock now for forgetting something 
this obvious ;-) .

Apart from the NULL check what more did I mess up? Should I send a fixup patch 
or do you want to do it?


> Now I can tell everyone to
> use this and refer to it.
> 
> > I've also attached my current rockchip pinctrl driver to show how it is
> > using this currently.
> 
> OK I might just merge it. If you take the rest of the patches through
> ARM SoC they will need to pull in my tree anyway if it's intended to
> go in this merge window.

go ahead if you like - this is the most current version of the driver and 
would be one patch less to worry about. It would after all come together 
during the merge window again.

And very basic boot of the SoC works even without the pinctrl driver, as the 
uart pins are of course set up by the bootloader.


Thanks
Heiko

  reply	other threads:[~2013-06-10 13:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 23:59 [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt Heiko Stübner
2013-06-08 23:59 ` [PATCH 1/2] pinctrl: add devicetree constants for simple generic pnconfig options Heiko Stübner
2013-06-09  0:00 ` [PATCH 2/2] pinctrl: add function to separate combined pinconfig values Heiko Stübner
2013-06-09  0:01 ` [EXAMPLE PATCH] pinctrl: add pinctrl driver for Rockchip SoCs Heiko Stübner
2013-06-10 12:55   ` Linus Walleij
2013-06-10 13:00   ` Linus Walleij
2013-06-10 13:10     ` Heiko Stübner
2013-06-10 13:35       ` [PATCH v2] " Heiko Stübner
2013-06-10 13:40       ` [EXAMPLE PATCH] " Linus Walleij
2013-06-10 18:23     ` Stephen Warren
2013-06-10 19:53       ` Rob Herring
2013-06-11  8:50       ` Linus Walleij
2013-06-10 12:52 ` [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt Linus Walleij
2013-06-10 13:06   ` Heiko Stübner [this message]
2013-06-10 13:39     ` Linus Walleij
2013-06-10 13:54       ` Heiko Stübner
2013-06-10 14:08         ` 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=201306101506.36098.heiko@sntech.de \
    --to=heiko@sntech.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).