linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Thomas Abraham'" <thomas.abraham@linaro.org>,
	"'Linus Walleij'" <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, grant.likely@secretlab.ca,
	rob.herring@calxeda.com, dong.aisheng@linaro.org,
	swarren@wwwdotorg.org, patches@linaro.org
Subject: RE: [PATCH v3 1/4] pinctrl: add samsung pinctrl and gpiolib driver
Date: Wed, 05 Sep 2012 06:45:16 +0900	[thread overview]
Message-ID: <226e01cd8ae6$928010b0$b7803210$%kim@samsung.com> (raw)
In-Reply-To: <CAJuYYwTD+vMg=YjUj4G0E-uakk=Y_SD+cUU22QSx0yRC50V75w@mail.gmail.com>

Thomas Abraham wrote:
> 
> On 3 September 2012 16:44, Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Thu, Aug 23, 2012 at 1:15 PM, Thomas Abraham
> > <thomas.abraham@linaro.org> wrote:
> >
> >> Add a new device tree enabled pinctrl and gpiolib driver for Samsung
> >> SoC's. This driver provides a common and extensible framework for all
> >> Samsung SoC's to interface with the pinctrl and gpiolib subsystems.
> This
> >> driver supports only device tree based instantiation and hence can be
> >> used only on those Samsung platforms that have device tree enabled.
> >>
> >> This driver is split into two parts: the pinctrl interface and the
> gpiolib
> >> interface. The pinctrl interface registers pinctrl devices with the
> pinctrl
> >> subsystem and gpiolib interface registers gpio chips with the gpiolib
> >> subsystem. The information about the pins, pin groups, pin functions
> and
> >> gpio chips, which are SoC specific, are parsed from device tree node.
> >>
> >> Cc: Linus Walleij <linus.walleij@linaro.org>
> >> Cc: Kukjin Kim <kgene.kim@samsung.com>
> >> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> >
> > Looks good to me, I saw Stephen had some minor comments and
> > I expect that you probably fix them before applying to the Samsung
> > tree so:
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > Feel free to push this through ARM SoC, I guess that's the plan?
> 
> Hi Linus,
> 
> Thanks for reviewing the Samsung pinctrl driver patches. I will do the
> changes that Stephen has listed and resubmit. I will request Samsung
> maintainer to consider the support for pinctrl driver for 3.7.
> 
Looks OK, I will apply updated patches Thomas said into Samsung tree.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.


  reply	other threads:[~2012-09-04 21:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 11:15 [PATCH v3 0/4] pinctrl: add support for samsung pinctrl driver Thomas Abraham
2012-08-23 11:15 ` [PATCH v3 1/4] pinctrl: add samsung pinctrl and gpiolib driver Thomas Abraham
2012-08-23 23:12   ` Stephen Warren
2012-08-24  4:25     ` Thomas Abraham
2012-09-03 11:14   ` Linus Walleij
2012-09-04 19:47     ` Thomas Abraham
2012-09-04 21:45       ` Kukjin Kim [this message]
2012-09-05  6:20         ` Thomas Abraham
2012-09-06 17:33           ` Stephen Warren
2012-09-06 22:03             ` Kukjin Kim
2012-09-05 13:50   ` Tomasz Figa
2012-09-05 15:19     ` Thomas Abraham
2012-08-23 11:15 ` [PATCH v3 2/4] pinctrl: add exynos4210 specific extensions for samsung pinctrl driver Thomas Abraham
2012-09-03 11:16   ` Linus Walleij
2012-08-23 11:15 ` [PATCH v3 3/4] gpio: exynos4: skip gpiolib registration if pinctrl driver is used Thomas Abraham
2012-08-23 11:15 ` [PATCH v3 4/4] ARM: EXYNOS: skip wakeup interrupt setup " Thomas Abraham
2012-09-03 11:17   ` 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='226e01cd8ae6$928010b0$b7803210$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dong.aisheng@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thomas.abraham@linaro.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).