linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] omapdss: use devm_clk_get()
Date: Wed, 10 Apr 2013 09:19:32 +0000	[thread overview]
Message-ID: <51652EA4.9010606@ti.com> (raw)
In-Reply-To: <516524B8.60205@ti.com>

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

On 2013-04-10 11:37, Archit Taneja wrote:
> On Wednesday 10 April 2013 01:43 PM, Tomi Valkeinen wrote:
>> On 2013-04-08 11:55, Archit Taneja wrote:
>>> Use devm_clk_get() instead of clk_get() for dss, and for outputs hdmi
>>> and venc.
>>> This reduces reduces code and simplifies error handling.
>>>
>>> Signed-off-by: Archit Taneja <archit@ti.com>
>>> ---
>>>   drivers/video/omap2/dss/dss.c  |   18 +++---------------
>>>   drivers/video/omap2/dss/hdmi.c |   16 ++--------------
>>>   drivers/video/omap2/dss/venc.c |   10 +---------
>>>   3 files changed, 6 insertions(+), 38 deletions(-)
>>>
>>> diff --git a/drivers/video/omap2/dss/dss.c
>>> b/drivers/video/omap2/dss/dss.c
>>> index 054c2a2..645b3bc 100644
>>> --- a/drivers/video/omap2/dss/dss.c
>>> +++ b/drivers/video/omap2/dss/dss.c
>>> @@ -767,13 +767,11 @@ int dss_dpi_select_source(enum omap_channel
>>> channel)
>>>   static int dss_get_clocks(void)
>>>   {
>>>       struct clk *clk;
>>> -    int r;
>>>
>>> -    clk = clk_get(&dss.pdev->dev, "fck");
>>> +    clk = devm_clk_get(&dss.pdev->dev, "fck");
>>>       if (IS_ERR(clk)) {
>>>           DSSERR("can't get clock fck\n");
>>> -        r = PTR_ERR(clk);
>>> -        goto err;
>>> +        return PTR_ERR(clk);
>>>       }
>>>
>>>       dss.dss_clk = clk;
>>> @@ -782,8 +780,7 @@ static int dss_get_clocks(void)
>>>           clk = clk_get(NULL, dss.feat->clk_name);
>>>           if (IS_ERR(clk)) {
>>>               DSSERR("Failed to get %s\n", dss.feat->clk_name);
>>> -            r = PTR_ERR(clk);
>>> -            goto err;
>>> +            return PTR_ERR(clk);
>>>           }
>>>       } else {
>>>           clk = NULL;
>>> @@ -792,21 +789,12 @@ static int dss_get_clocks(void)
>>>       dss.dpll4_m4_ck = clk;
>>>
>>>       return 0;
>>> -
>>> -err:
>>> -    if (dss.dss_clk)
>>> -        clk_put(dss.dss_clk);
>>> -    if (dss.dpll4_m4_ck)
>>> -        clk_put(dss.dpll4_m4_ck);
>>> -
>>> -    return r;
>>>   }
>>
>> Why didn't you use devm_clk_get for the dpll4_m4_ck clock also?
> 
> clk_get of dpll4_m4_ck isn't tied to a device:
> 
>     clk = clk_get(NULL, dss.feat->clk_name);
> 
> We can't use devm_clk_get() if we don't tie it to a device, right?

Ah, true.

> I think the dss.dss_clk clock above is same as the dpll4_m4_ck for all
> OMAPs. We could probably remove the dpll4_m4_clk all together, and use
> dss_clk to get the rate of DSS_FCK coming from PRCM.

Hmm, no, if I recall right, dpll4_m4_clk is the parent of dss clock (or
parent of the parent of...), and the dss_fck_multiplier affects the
resulting dss fck. Or something like that. It's a bit messy, especially
as we can't just use the dss fck to change the rate, we need to change
the rate at the parent for some reason.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

  reply	other threads:[~2013-04-10  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  8:56 [PATCH] omapdss: use devm_clk_get() Archit Taneja
2013-04-10  8:13 ` Tomi Valkeinen
2013-04-10  8:49   ` Archit Taneja
2013-04-10  9:19     ` Tomi Valkeinen [this message]
2013-04-10  9:40       ` Archit Taneja
2013-04-10  9:32         ` Tomi Valkeinen
2013-04-10  9:41         ` Archit Taneja

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=51652EA4.9010606@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@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).