linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: Enrico <ebutera@users.berlios.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Enric Balletbo Serra <eballetbo@gmail.com>
Subject: Re: [PATCH 00/11] OMAP3 ISP BT.656 support
Date: Tue, 24 Jun 2014 19:19:22 +0200	[thread overview]
Message-ID: <53A9B31A.80607@herbrechtsmeier.net> (raw)
In-Reply-To: <CA+2YH7urbO6C-a6UMB+1JKN2z7F0CDmqh0184cCzXHbW1ADfXA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

Am 24.06.2014 17:19, schrieb Enrico:
> On Tue, May 27, 2014 at 10:38 AM, Enrico <ebutera@users.berlios.de> wrote:
>> On Mon, May 26, 2014 at 9:50 PM, Laurent Pinchart
>> <laurent.pinchart@ideasonboard.com> wrote:
>>> Hello,
>>>
>>> This patch sets implements support for BT.656 and interlaced formats in the
>>> OMAP3 ISP driver. Better late than never I suppose, although given how long
>>> this has been on my to-do list there's probably no valid excuse.
>> Thanks Laurent!
>>
>> I hope to have time soon to test it :)
> i wanted to try your patches but i'm having a problem (probably not
> caused by your patches).
>
> I merged media_tree master and omap3isp branches, applied your patches
> and added camera platform data in pdata-quirks, but when loading the
> omap3-isp driver i have:
>
> omap3isp: clk_set_rate for cam_mclk failed
>
> The returned value from clk_set_rate is -22 (EINVAL), but i can't see
> any other debug message to track it down. Any ides?
> I'm testing it on an igep proton (omap3530 version).
Hi Enrico,

please test the attached patch. It is based on Laurent's patches for the 
clock and boot testes on an Gumstix Overo with an OMAP3530.

Regards,
   Stefan


[-- Attachment #2: 0021-ARM-dts-set-ti-set-rate-parent-for-dpll4_m5x2-clock.patch --]
[-- Type: text/x-patch, Size: 1034 bytes --]

>From 9f8162ddebf7636e60101f0831d071e73ab6df75 Mon Sep 17 00:00:00 2001
From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Date: Fri, 13 Jun 2014 18:15:56 +0200
Subject: [PATCH 21/25] ARM: dts: set 'ti,set-rate-parent' for dpll4_m5x2 clock

Set 'ti,set-rate-parent' property for the dpll4_m5x2_ck clock, which
is used for the ISP functional clock. This fixes the OMAP3 ISP driver's
clock rate configuration on OMAP34xx, which needs the rate to be
propagated properly to the divider node (dpll4_m5_ck).

Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
---
 arch/arm/boot/dts/omap3xxx-clocks.dtsi | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/boot/dts/omap3xxx-clocks.dtsi b/arch/arm/boot/dts/omap3xxx-clocks.dtsi
index 25adab1..beeff7c 100644
--- a/arch/arm/boot/dts/omap3xxx-clocks.dtsi
+++ b/arch/arm/boot/dts/omap3xxx-clocks.dtsi
@@ -465,6 +465,7 @@
 		ti,bit-shift = <0x1e>;
 		reg = <0x0d00>;
 		ti,set-bit-to-disable;
+		ti,set-rate-parent;
 	};
 
 	dpll4_m6_ck: dpll4_m6_ck {
-- 
2.0.0


  reply	other threads:[~2014-06-24 17:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 19:50 [PATCH 00/11] OMAP3 ISP BT.656 support Laurent Pinchart
2014-05-26 19:50 ` [PATCH 01/11] v4l: subdev: Extend default link validation to cover field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 02/11] omap3isp: Don't ignore subdev streamoff failures Laurent Pinchart
2014-05-26 19:50 ` [PATCH 03/11] omap3isp: Remove boilerplate disclaimer and FSF address Laurent Pinchart
2014-05-26 19:50 ` [PATCH 04/11] omap3isp: Move non-critical code out of the mutex-protected section Laurent Pinchart
2014-05-26 19:50 ` [PATCH 05/11] omap3isp: Default to progressive field order when setting the format Laurent Pinchart
2014-05-26 19:50 ` [PATCH 06/11] omap3isp: video: Validate the video node field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 07/11] omap3isp: ccdc: Simplify the configuration function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 08/11] omap3isp: ccdc: Simplify the ccdc_isr_buffer() function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 09/11] omap3isp: ccdc: Add basic support for interlaced video Laurent Pinchart
2014-05-26 21:12   ` Sakari Ailus
2014-05-26 19:50 ` [PATCH 10/11] omap3isp: ccdc: Support the interlaced field orders at the CCDC output Laurent Pinchart
2014-05-26 19:50 ` [PATCH 11/11] omap3isp: ccdc: Add support for BT.656 YUV format at the CCDC input Laurent Pinchart
2014-05-26 21:18 ` [PATCH 00/11] OMAP3 ISP BT.656 support Sakari Ailus
2014-05-27  8:38 ` Enrico
2014-06-24 15:19   ` Enrico
2014-06-24 17:19     ` Stefan Herbrechtsmeier [this message]
2014-07-01 20:24       ` Laurent Pinchart
2014-07-04 11:21         ` Stefan Herbrechtsmeier
2014-06-26 16:18     ` Enrico
2014-07-01 20:17       ` Laurent Pinchart
2014-07-22 15:52     ` Enrico
2014-07-22 16:04       ` Laurent Pinchart
2014-07-22 16:26         ` Enrico
2014-07-22 16:32           ` Laurent Pinchart
2014-07-23 13:54             ` Enrico
2014-07-23 13:57               ` Enrico
2014-07-30 21:01                 ` Laurent Pinchart
2014-07-31 10:21                   ` Enrico
2014-08-01 13:46                     ` Laurent Pinchart
     [not found]         ` <1406046034.73192.YahooMailNeo@web162404.mail.bf1.yahoo.com>
2014-07-22 16:27           ` Laurent Pinchart

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=53A9B31A.80607@herbrechtsmeier.net \
    --to=stefan@herbrechtsmeier.net \
    --cc=eballetbo@gmail.com \
    --cc=ebutera@users.berlios.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.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).