Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC 0/3] ARM: S5P: Add common DPHY control code for MIPI-CSIS/MIPI-DSIM devices
Date: Thu, 03 Mar 2011 13:43:02 +0900	[thread overview]
Message-ID: <01a701cbd95d$9873c160$c95b4420$%kim@samsung.com> (raw)
In-Reply-To: <1299087289-29926-1-git-send-email-s.nawrocki@samsung.com>

Sylwester Nawrocki wrote:
> 
> Hello,
> 
> the following patch series adds a common platform code to enable control
> of MIPI-CSI receiver's DPHY from within it's V4L2 subdev driver. The
driver
> is supposed to support possibly all S5P SoCs variants and the PHY handling
> details need to be hidden in the platform code. The functionality behind
> "dphy_csis" clocks is not exact a functionality of the clock, but they
have
> common features. If the clock API rules are to strict to accept this kind
> of usage then I'm willing to create some intermediate layer that will
finally
> solve PHY handling for MIPI-CSI, MIPI-DSIM, USB, SATA.. devices, without
> issues
> on a common kernel binary for multiple boards.
> 
> 
> The patch series contains:
> [PATCH 1/3] ARM: S5P: Rename MIPI-CSIS header and update Copyright
> [PATCH 2/3] ARM: S5PV210: Add clock entries for MIPI DPHY control
> [PATCH 3/3] ARM: EXYNOS4: Add clock entries for MIPI DPHY control
> 
> Rebased onto kgene-for-next branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> 

Maybe we discussed about this ago.
I remember, we agree that to control phy cannot be handled in clock part.

And didn't say to make some kind of common s5p phy setup/control function?
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-January/038038.ht
ml

I thought it is possible to make it even though some registers is in
different place.

Thanks.

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

  parent reply	other threads:[~2011-03-03  4:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 17:34 [PATCH/RFC 0/3] ARM: S5P: Add common DPHY control code for MIPI-CSIS/MIPI-DSIM devices Sylwester Nawrocki
2011-03-02 17:34 ` [PATCH 1/3] ARM: S5P: Rename MIPI-CSIS header and update Copyright Sylwester Nawrocki
2011-03-03  4:33   ` Kukjin Kim
2011-03-03  9:34     ` Sylwester Nawrocki
2011-03-02 17:34 ` [PATCH 2/3] ARM: S5PV210: Add clock entries for MIPI DPHY control Sylwester Nawrocki
2011-03-02 17:34 ` [PATCH 3/3] ARM: EXYNOS4: " Sylwester Nawrocki
2011-03-03  4:43 ` Kukjin Kim [this message]
2011-03-03 19:04   ` [PATCH v2 0/3] ARM: S5P: Add D-PHY control platform helpers for MIPI-CSIS/DSIM drivers Sylwester Nawrocki
2011-03-08 23:05     ` Kukjin Kim
2011-03-03 19:04   ` [PATCH v2 1/3] ARM: S5P: Rename MIPI-CSIS driver header and update Copyright Sylwester Nawrocki
2011-03-03 19:04   ` [PATCH v2 2/3] ARM: S5P: Extend MIPI-CSIS platform_data with the PHY control callback Sylwester Nawrocki
2011-03-09 15:44     ` [PATCH v2] " Sylwester Nawrocki
2011-03-03 19:04   ` [PATCH v2 3/3] ARM: S5P: Add support for common MIPI CSIS/DSIM D-PHY control Sylwester Nawrocki
2011-03-09 22:55     ` Kukjin Kim
2011-03-10 11:06       ` [PATCH v3 0/3] ARM: S5P: Add platform helpers for MIPI-CSIS/DSIM DPHY Sylwester Nawrocki
2011-03-10 11:06       ` [PATCH v3 1/3] ARM: S5P: Rename MIPI-CSIS driver header and update Copyright Sylwester Nawrocki
2011-03-10 11:13         ` Kukjin Kim
2011-03-10 11:06       ` [PATCH v3 2/3] ARM: S5P: Extend MIPI-CSIS platform_data with the PHY control callback Sylwester Nawrocki
2011-03-10 11:29         ` Kukjin Kim
2011-03-10 11:06       ` [PATCH v3 3/3] ARM: S5P: Add support for common MIPI CSIS/DSIM D-PHY control Sylwester Nawrocki
2011-03-10 11:20       ` [PATCH v2 " 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='01a701cbd95d$9873c160$c95b4420$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --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