mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanho Park <chanho61.park@samsung.com>
To: linus.walleij@linaro.org, swarren@nvidia.com, Baohua.Song@csr.com
Cc: linux-kernel@vger.kernel.org, Chanho Park <chanho61.park@samsung.com>
Subject: [PATCH 0/2] add support for partial pin space
Date: Tue, 03 Jan 2012 16:47:49 +0900	[thread overview]
Message-ID: <1325576871-9397-1-git-send-email-chanho61.park@samsung.com> (raw)

A pin space of current pinctrl driver always start with zero-based pin
number. And pins are enumerated from 0 to a max pin number. If there are
two pins (one is 0, another is 1000), we always enumerate from 0 to 1000
for just only two pins. This patch enables to start non-zero based pin
number and to enumerate actually owned pins.

For example, there is a system which has huge(500 or 1000) pins. If muxing
or controlling pins are small, we just define such small pins instead of
whole pins.

Chanho Park (2):
  pinctrl: correct a offset while enumerating pins
  pinctrl: remove unnecessary max pin number

 drivers/pinctrl/core.c          |   19 ++++++++++---------
 drivers/pinctrl/pinconf.c       |    9 +++++----
 drivers/pinctrl/pinctrl-sirf.c  |    1 -
 drivers/pinctrl/pinctrl-u300.c  |    1 -
 drivers/pinctrl/pinmux.c        |    9 +++++----
 include/linux/pinctrl/pinctrl.h |    5 -----
 6 files changed, 20 insertions(+), 24 deletions(-)

-- 
1.7.5.4


             reply	other threads:[~2012-01-03  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03  7:47 Chanho Park [this message]
2012-01-03  7:47 ` [PATCH 1/2] pinctrl: correct a offset while enumerating pins Chanho Park
2012-01-03  7:58   ` Linus Walleij
2012-01-03  8:37     ` Chanho Park
2012-01-04  9:37       ` Linus Walleij
2012-01-03  7:47 ` [PATCH 2/2] pinctrl: remove unnecessary max pin number Chanho Park
2012-01-03  7:57 ` [PATCH 0/2] add support for partial pin space Linus Walleij
2012-01-03  8:27   ` Chanho Park

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=1325576871-9397-1-git-send-email-chanho61.park@samsung.com \
    --to=chanho61.park@samsung.com \
    --cc=Baohua.Song@csr.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    /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

all inboxes | Powered by JetHome®