From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Shaik Ameer Basha <shaik.ameer@samsung.com>
Cc: linux-media@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-samsung-soc@vger.kernel.org, s.nawrocki@samsung.com,
shaik.samsung@gmail.com
Subject: Re: [RFC 05/12] ARM: EXYNOS: Add devicetree node for mipi-csis driver for exynos5
Date: Sun, 10 Mar 2013 21:54:16 +0100 [thread overview]
Message-ID: <513CF2F8.4000802@gmail.com> (raw)
In-Reply-To: <1362570838-4737-6-git-send-email-shaik.ameer@samsung.com>
On 03/06/2013 12:53 PM, Shaik Ameer Basha wrote:
> This patch adds necessary source definations needed for mipi-csis
> driver and adds devicetree node for exynos5250.
>
> Signed-off-by: Shaik Ameer Basha<shaik.ameer@samsung.com>
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 18 ++++++++++++++++++
> arch/arm/mach-exynos/clock-exynos5.c | 16 ++++++++++++++--
> arch/arm/mach-exynos/include/mach/map.h | 3 +++
> arch/arm/mach-exynos/mach-exynos5-dt.c | 4 ++++
> 4 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index 3a2cd9a..4fff98b 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -47,6 +47,8 @@
> i2c6 =&i2c_6;
> i2c7 =&i2c_7;
> i2c8 =&i2c_8;
> + csis0 =&csis_0;
> + csis1 =&csis_1;
> };
>
> gic:interrupt-controller@10481000 {
> @@ -357,4 +359,20 @@
> reg =<0x14450000 0x10000>;
> interrupts =<0 94 0>;
> };
> +
> + csis_0: csis@13C20000 {
> + compatible = "samsung,exynos5250-csis";
> + reg =<0x13C20000 0x4000>;
> + interrupts =<0 79 0>;
> + bus-width =<4>;
> + status = "disabled";
> + };
> +
> + csis_1: csis@13C30000 {
> + compatible = "samsung,exynos5250-csis";
> + reg =<0x13C30000 0x4000>;
> + interrupts =<0 80 0>;
> + bus-width =<4>;
Shouldn't this be 2 ? Anyway what's the point of adding this node here
only to move it in a subsequent patch ? I guess you should first add
'camera' node and then have further patches adding relevant device nodes.
> + status = "disabled";
> + };
> };
> diff --git a/arch/arm/mach-exynos/clock-exynos5.c b/arch/arm/mach-exynos/clock-exynos5.c
> index e9d7b80..34a22ff 100644
> --- a/arch/arm/mach-exynos/clock-exynos5.c
> +++ b/arch/arm/mach-exynos/clock-exynos5.c
This file is already removed in Kukjin's for-next tree.
And for dts changes I would start the patch summary line with "ARM: dts:".
> @@ -859,6 +859,16 @@ static struct clk exynos5_init_clocks_off[] = {
> .enable = exynos5_clk_ip_gscl_ctrl,
> .ctrlbit = (1<< 3),
> }, {
> + .name = "csis",
> + .devname = "s5p-mipi-csis.0",
> + .enable = exynos5_clk_ip_gscl_ctrl,
> + .ctrlbit = (1<< 5),
> + }, {
> + .name = "csis",
> + .devname = "s5p-mipi-csis.1",
> + .enable = exynos5_clk_ip_gscl_ctrl,
> + .ctrlbit = (1<< 6),
> + }, {
next prev parent reply other threads:[~2013-03-10 20:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:53 [RFC 00/12] Adding media device driver for Exynos imaging subsystem Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 01/12] media: s5p-fimc: modify existing mdev to use common pipeline Shaik Ameer Basha
2013-03-10 22:00 ` Sylwester Nawrocki
2013-03-11 6:41 ` Shaik Ameer Basha
2013-03-14 0:01 ` Sylwester Nawrocki
2013-03-06 11:53 ` [RFC 02/12] fimc-lite: Adding Exynos5 compatibility to fimc-lite driver Shaik Ameer Basha
2013-03-10 20:36 ` Sylwester Nawrocki
2013-03-11 6:41 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 03/12] media: fimc-lite: Adding support for Exynos5 Shaik Ameer Basha
2013-03-10 20:39 ` Sylwester Nawrocki
2013-03-11 6:43 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 04/12] s5p-csis: Adding Exynos5250 compatibility Shaik Ameer Basha
2013-03-10 20:40 ` Sylwester Nawrocki
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-12 13:52 ` Sylwester Nawrocki
2013-03-06 11:53 ` [RFC 05/12] ARM: EXYNOS: Add devicetree node for mipi-csis driver for exynos5 Shaik Ameer Basha
2013-03-10 20:54 ` Sylwester Nawrocki [this message]
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-10 20:57 ` Sylwester Nawrocki
2013-03-11 6:58 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 06/12] ARM: EXYNOS: Add devicetree node for FIMC-LITE " Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 07/12] media: exynos5-is: Adding media device " Shaik Ameer Basha
2013-03-10 22:28 ` Sylwester Nawrocki
2013-03-11 6:59 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 08/12] ARM: dts: add camera specific pinctrl nodes for Exynos5250 SoC Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 09/12] ARM: dts: Adding pinctrl support to Exynos5250 i2c nodes Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 10/12] ARM: dts: Adding media device nodes to Exynos5 SoCs Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 11/12] media: m5mols: Adding dt support to m5mols driver Shaik Ameer Basha
2013-03-23 11:56 ` Sylwester Nawrocki
2013-03-25 5:39 ` Shaik Ameer Basha
2013-03-06 11:53 ` [RFC 12/12] ARM: dts: Add camera node to exynos5250-smdk5250.dts Shaik Ameer Basha
[not found] ` <1362570838-4737-13-git-send-email-shaik.ameer-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-03-23 12:18 ` Sylwester Nawrocki
2013-03-10 20:36 ` [RFC 00/12] Adding media device driver for Exynos imaging subsystem Sylwester Nawrocki
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=513CF2F8.4000802@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.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;
as well as URLs for NNTP newsgroup(s).