devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Linux OMAP Mailing List" <linux-omap@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	LAK <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: am437x-gp-evm: add DT nodes for ov2659 sensor
Date: Tue, 17 Mar 2015 01:20:04 +0000	[thread overview]
Message-ID: <CA+V-a8uWqjze32ukOGonQAACByPmW6WDbpFrA9EFipnNJeD58A@mail.gmail.com> (raw)
In-Reply-To: <20150316221740.GQ12397@atomide.com>

Hi Tony,

On Mon, Mar 16, 2015 at 10:17 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Lad Prabhakar <prabhakar.csengg@gmail.com> [150312 16:38]:
>> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
>>
>> this patch does the following:
>> 1: adds DT node for fixed oscillator.
>> 2: adds DT node entries for ov2659 sensor
>> 3: adds remote-endpoint entry for VPFE.
>>
>> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>
> Applying into omap-for-v4.1/dt thanks.
>
I would like to get this one in via media tree to avoid dependency
as I am still waiting for Acks from DT maintainers for the sensor
driver.

If I can get your Ack on this I'll queue it up along with sensor
driver via media tree.

Cheers,
--Prabhakar Lad

> Tony
>
>> ---
>>  Note this patch depends on
>>  https://patchwork.kernel.org/patch/6000161/
>>
>>  arch/arm/boot/dts/am437x-gp-evm.dts | 42 +++++++++++++++++++++++++++++++++++--
>>  1 file changed, 40 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
>> index f84d971..195f452 100644
>> --- a/arch/arm/boot/dts/am437x-gp-evm.dts
>> +++ b/arch/arm/boot/dts/am437x-gp-evm.dts
>> @@ -106,6 +106,14 @@
>>                       };
>>               };
>>       };
>> +
>> +     /* fixed 12MHz oscillator */
>> +     refclk: oscillator {
>> +             #clock-cells = <0>;
>> +             compatible = "fixed-clock";
>> +             clock-frequency = <12000000>;
>> +     };
>> +
>>  };
>>
>>  &am43xx_pinmux {
>> @@ -404,6 +412,21 @@
>>                       regulator-always-on;
>>               };
>>       };
>> +
>> +     ov2659@30 {
>> +             compatible = "ovti,ov2659";
>> +             reg = <0x30>;
>> +
>> +             clocks = <&refclk 0>;
>> +             clock-names = "xvclk";
>> +
>> +             port {
>> +                     ov2659_0: endpoint {
>> +                             remote-endpoint = <&vpfe1_ep>;
>> +                             link-frequencies = /bits/ 64 <70000000>;
>> +                     };
>> +             };
>> +     };
>>  };
>>
>>  &i2c1 {
>> @@ -423,6 +446,21 @@
>>               touchscreen-size-x = <1024>;
>>               touchscreen-size-y = <600>;
>>       };
>> +
>> +     ov2659@30 {
>> +             compatible = "ovti,ov2659";
>> +             reg = <0x30>;
>> +
>> +             clocks = <&refclk 0>;
>> +             clock-names = "xvclk";
>> +
>> +             port {
>> +                     ov2659_1: endpoint {
>> +                             remote-endpoint = <&vpfe0_ep>;
>> +                             link-frequencies = /bits/ 64 <70000000>;
>> +                     };
>> +             };
>> +     };
>>  };
>>
>>  &epwmss0 {
>> @@ -626,7 +664,7 @@
>>
>>       port {
>>               vpfe0_ep: endpoint {
>> -                     /* remote-endpoint = <&sensor>; add once we have it */
>> +                     remote-endpoint = <&ov2659_1>;
>>                       ti,am437x-vpfe-interface = <0>;
>>                       bus-width = <8>;
>>                       hsync-active = <0>;
>> @@ -643,7 +681,7 @@
>>
>>       port {
>>               vpfe1_ep: endpoint {
>> -                     /* remote-endpoint = <&sensor>; add once we have it */
>> +                     remote-endpoint = <&ov2659_0>;
>>                       ti,am437x-vpfe-interface = <0>;
>>                       bus-width = <8>;
>>                       hsync-active = <0>;
>> --
>> 2.1.0
>>

  reply	other threads:[~2015-03-17  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 23:38 [PATCH] ARM: dts: am437x-gp-evm: add DT nodes for ov2659 sensor Lad Prabhakar
2015-03-16 22:17 ` Tony Lindgren
2015-03-17  1:20   ` Lad, Prabhakar [this message]
2015-03-17  2:23     ` Tony Lindgren
     [not found]       ` <20150317022344.GB31346-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-04-10 20:22         ` Lad, Prabhakar
     [not found]           ` <CA+V-a8u-Y7M9ynJDD05=XeMjZMsb_0Utd-TuwJzEuRziPksvGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-01  8:55             ` Lad, Prabhakar
     [not found]   ` <20150316221740.GQ12397-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-05-20 18:14     ` Tony Lindgren

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=CA+V-a8uWqjze32ukOGonQAACByPmW6WDbpFrA9EFipnNJeD58A@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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).