From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] mfd: as3722: add clock driver as mfd-sub device for the ams AS3722
Date: Tue, 29 Oct 2013 08:21:22 -0700 [thread overview]
Message-ID: <20131029152122.GD4231@lee--X1> (raw)
In-Reply-To: <1383049205-29620-2-git-send-email-ldewangan@nvidia.com>
On Tue, 29 Oct 2013, Laxman Dewangan wrote:
> Device ams AS3722 supports the one 32KHz clock output. The clock control
> support is provided through clock driver.
>
> Add clock driver as mfd sub device to probe the clock driver.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> Documentation/devicetree/bindings/mfd/as3722.txt | 9 +++++++++
> drivers/mfd/as3722.c | 3 +++
You need to seperate the DT binding from the drivers/mfd changes.
The MFD changes are fine of course.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: sameo@linux.intel.com, mturquette@linaro.org,
dwmw2@infradead.org, anton@enomsg.org, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, rob.herring@calxeda.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] mfd: as3722: add clock driver as mfd-sub device for the ams AS3722
Date: Tue, 29 Oct 2013 08:21:22 -0700 [thread overview]
Message-ID: <20131029152122.GD4231@lee--X1> (raw)
In-Reply-To: <1383049205-29620-2-git-send-email-ldewangan@nvidia.com>
On Tue, 29 Oct 2013, Laxman Dewangan wrote:
> Device ams AS3722 supports the one 32KHz clock output. The clock control
> support is provided through clock driver.
>
> Add clock driver as mfd sub device to probe the clock driver.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> Documentation/devicetree/bindings/mfd/as3722.txt | 9 +++++++++
> drivers/mfd/as3722.c | 3 +++
You need to seperate the DT binding from the drivers/mfd changes.
The MFD changes are fine of course.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-10-29 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 12:20 [PATCH 0/4] clk/power: add clock and power off driver for AS3722 Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` [PATCH 1/4] mfd: as3722: add clock driver as mfd-sub device for the ams AS3722 Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 15:21 ` Lee Jones [this message]
2013-10-29 15:21 ` Lee Jones
2013-10-29 12:20 ` [PATCH 2/4] clk: as3722: add clock driver for " Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` [PATCH 3/4] mfd: AS3722: add dt node properties for system power controller Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` [PATCH 4/4] power: reset: as3722: add power-off driver Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
2013-10-29 12:20 ` Laxman Dewangan
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=20131029152122.GD4231@lee--X1 \
--to=lee.jones@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.