linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: OMAP2+: Add support to parse optional clk info from DT
Date: Wed, 14 Aug 2013 08:39:44 -0500	[thread overview]
Message-ID: <520B88A0.6080806@ti.com> (raw)
In-Reply-To: <520B8409.5000708@ti.com>

On 08/14/2013 08:20 AM, Rajendra Nayak wrote:
> On Wednesday 14 August 2013 06:18 PM, Nishanth Menon wrote:
>> Hi Rajendra,
>>
>> On Tue, Jul 23, 2013 at 1:24 AM, Rajendra Nayak <rnayak@ti.com> wrote:
>> [..]
>>> diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
>>> index 12fa589..e5c804b 100644
>>> --- a/arch/arm/mach-omap2/omap_hwmod.c
>>> +++ b/arch/arm/mach-omap2/omap_hwmod.c
>>> @@ -805,6 +805,65 @@ static int _init_interface_clks(struct omap_hwmod *oh)
>>>          return ret;
>>>   }
>>>
>>> +static const char **_parse_opt_clks_dt(struct omap_hwmod *oh,
>>> +                                      struct device_node *np,
>>> +                                      int *opt_clks_cnt)
>>> +{
>>> +       int i, clks_cnt;
>>> +       const char *clk_name;
>>> +       const char **opt_clk_names;
>>> +
>>> +       clks_cnt = of_property_count_strings(np, "clock-names");
>>> +       if (!clks_cnt)
>>> +               return NULL;
>>> +
>>> +       opt_clk_names = kzalloc(sizeof(char *)*clks_cnt, GFP_KERNEL);
>>> +       if (!opt_clk_names)
>>> +               return NULL;
>>> +
>>> +       for (i = 0; i < clks_cnt; i++) {
>>> +               of_property_read_string_index(np, "clock-names", i, &clk_name);
>>> +               if (!strcmp(clk_name, "fck"))
>>
>> Could we instead parse for names that are "optional,role_name" instead
>> of assuming anything other than fck is optional clocks?
>
> you mean look for anything with optional,*? because the role names would change.
>

yes. the idea being, we now have a meaning to the clock name - there are 
two types of clocks here.. functional and optional, we *might* have 
facility to add interface clock(we dont know interface clock handling 
yet, but something in the future).. we might increase the support for 
number of functional clocks.. it might help to keep the format such that 
it is a "bit extendable".

>>
>>> +                       continue;
>>> +               opt_clks_cnt++;
>>> +               opt_clk_names[i] = clk_name;
>>> +       }
>>> +       return opt_clk_names;
>>> +}
>>> +
>> [...]
>> --
>> Regards,
>> Nishanth Menon
>>
>


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2013-08-14 13:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23  6:24 [PATCH 0/3] OMAP2+: hwmod: Add support to parse clock info from DT Rajendra Nayak
2013-07-23  6:24 ` [PATCH 1/3] ARM: OMAP2+: Add support to parse 'main_clk' " Rajendra Nayak
2013-08-14 12:50   ` menon.nishanth at gmail.com
2013-07-23  6:24 ` [PATCH 2/3] ARM: OMAP2+: Add support to parse optional clk " Rajendra Nayak
2013-08-14 12:48   ` Nishanth Menon
2013-08-14 13:20     ` Rajendra Nayak
2013-08-14 13:39       ` Nishanth Menon [this message]
2013-08-14 13:41         ` Rajendra Nayak
2013-08-14 13:49         ` Mark Rutland
2013-08-14 13:57           ` Russell King - ARM Linux
2013-08-14 13:58           ` Nishanth Menon
2013-08-14 14:05             ` Rajendra Nayak
2013-08-14 14:08               ` Rajendra Nayak
2013-08-14 14:13               ` Mark Rutland
2013-08-14 14:20                 ` Rajendra Nayak
2013-08-14 14:41                   ` Nishanth Menon
2013-08-14 14:08             ` Mark Rutland
2013-08-14 14:13               ` Rajendra Nayak
2013-08-14 13:45   ` Mark Rutland
2013-08-14 13:54     ` Rajendra Nayak
2013-08-14 13:59       ` Mark Rutland
2013-07-23  6:24 ` [PATCH 3/3] ARM: OMAP4: dts: Add main and optional clock data into DT Rajendra Nayak
2013-08-20 23:57   ` Paul Walmsley
2013-08-21  8:28     ` Rajendra Nayak

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=520B88A0.6080806@ti.com \
    --to=nm@ti.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;
as well as URLs for NNTP newsgroup(s).