All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Karicheri, Muralidharan" <m-karicheri2@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>
Subject: RE: [PATCH - v3 4/4] DaVinci - vpfe-capture-converting ccdc drivers to platform driver
Date: Thu, 7 Jan 2010 12:18:18 -0600	[thread overview]
Message-ID: <A69FA2915331DC488A831521EAE36FE40162D43099@dlee06.ent.ti.com> (raw)
In-Reply-To: <878wcbkx60.fsf@deeprootsystems.com>

Kevin,

>
>OK, I'm not extremely familar with the whole video architecture here,
>but are all of these drivers expected to be doing clk_get() and
>clk_enable()?
>

[MK]Many IPs on DaVinci VPFE would require vpss master clock. So
it is better to do the way I have done in my patch. So it is expected
that clk_get, clk_enable etc are called from other drivers as well.

>I thought the point of moving the clocks into the CCDC driver was so that
>the clock management was done in a single, shared space.
>

[MK] No. The CCDC IP is used across DaVinci and OMAP SOCs. The clock is named differently on OMAP, but the IP requires two clocks. So we named
them as "master" and "slave" as a generic name. OMAP, patform code will be mapping master and slave clocks to their respective clocks. We had discussed this in the email chain.

Murali
>Kevin
>
>>>> Your earlier suggestion was to use as follows :-
>>>>
>>>> -	CLK(NULL, "vpss_master", &vpss_master_clk),
>>>> -	CLK(NULL, "vpss_slave", &vpss_slave_clk),
>>>> +	CLK("vpfe-capture", "master", &vpss_master_clk),
>>>> +	CLK("vpfe-capture", "slave", &vpss_slave_clk),
>>>>
>>>> I am not sure if the following will work so that it can be used across
>>>> multiple drivers.
>>>>
>>>> +	CLK(NULL, "master", &vpss_master_clk),
>>>> +	CLK(NULL, "slave", &vpss_slave_clk),
>>>>
>>>> If yes, I can re-do this patch. Please confirm.
>>>
>>>No, this will not work.  You need a dev_id field so that matching
>>>is done using the struct device.
>>>
>>>My original suggestion was when you had the VPFE driver doing the
>>>clk_get().  Now that it's in CCDC, maybe it should look like this.
>>>
>>>-	CLK(NULL, "vpss_master", &vpss_master_clk),
>>>-	CLK(NULL, "vpss_slave", &vpss_slave_clk),
>>>+	CLK("ccdc", "master", &vpss_master_clk),
>>>+	CLK("ccdc", "slave", &vpss_slave_clk),
>>>
>>>Kevin

  reply	other threads:[~2010-01-07 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 16:37 [PATCH - v3 4/4] DaVinci - vpfe-capture-converting ccdc drivers to platform driver m-karicheri2
2009-12-15 16:37 ` [PATCH - v3 2/4] V4L - vpfe capture - convert dm355 ccdc driver to a " m-karicheri2
2009-12-15 16:37   ` [PATCH - v3 3/4] V4L - vpfe capture - convert dm644x ccdc module " m-karicheri2
2009-12-15 16:37     ` [PATCH - v3 1/4] V4L - vpfe_capture - remove clock and ccdc resource handling m-karicheri2
2010-01-05 23:28 ` [PATCH - v3 4/4] DaVinci - vpfe-capture-converting ccdc drivers to platform driver Kevin Hilman
2010-01-06 14:44   ` Karicheri, Muralidharan
2010-01-06 16:04     ` Kevin Hilman
2010-01-06 16:20       ` Karicheri, Muralidharan
2010-01-06 16:36         ` Kevin Hilman
2010-01-07 18:18           ` Karicheri, Muralidharan [this message]
2010-01-07 19:43             ` Kevin Hilman
2010-01-07 21:33               ` Karicheri, Muralidharan
2010-01-07 21:50                 ` Kevin Hilman
2010-01-07 23:25                   ` Karicheri, Muralidharan
2010-01-08  9:06                     ` Hiremath, Vaibhav
2010-01-08 15:10                       ` Kevin Hilman
2010-01-11  4:36                         ` Hiremath, Vaibhav

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=A69FA2915331DC488A831521EAE36FE40162D43099@dlee06.ent.ti.com \
    --to=m-karicheri2@ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=hverkuil@xs4all.nl \
    --cc=khilman@deeprootsystems.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 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.