From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Thomas Abraham <thomas.abraham@linaro.org>
Cc: banajit.g@samsung.com,
RAJESHWARI S SHINDE <rajeshwari.s@samsung.com>,
PADMAVATHI VENNA <padma.v@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: Add clkdev support to HSMMC
Date: Wed, 31 Aug 2011 14:56:32 +0200 [thread overview]
Message-ID: <4E5E2F80.3010005@samsung.com> (raw)
In-Reply-To: <CAJuYYwRmEdvo684vP+pRo2XyyPbyxNOMobMVr4TFLUDCv9HHew@mail.gmail.com>
Hi Thomas,
On 08/31/2011 12:13 PM, Thomas Abraham wrote:
>
> [...]
>
>
>>> 3) In the proposed implementation where we create connection ids only for the
>>> bus clocks we are creating an extra node for the same in the clkdev table,
>>
>>> where as the clock is getting registered only once with the kernel.
>>
>> I don't agree with this last statement, the same struct clk is added to
>> the list of clocks known by the system twice, in s3c24xx_register_clocks()
>> and clkdev_add_table(). This is only what I have been pointing out.
>> Please correct me, if I missed anything.
>
> s3c24xx_register_clock and clkdev_add_table add one instance of
> "struct clk_lookup" each (with different connections ids) but both of
> these "struct clk_lookup" instances point to the same "struct clk"
> instance.
Yes, that's what happens in Banajit's code.
>
> So, is two instances of "struct clk_lookup" pointing to the same
> "struct clk" instance the concern in this case?
No, I don't see this as a problem. Just wanted to get things clarified.
And to suggest that we could avoid having re-created struct clk and struct
clk_clksrc arrays for s3c24xx_register_clocks() and s3c_register_clksrc()
functions. However I don't consider this a significant issue.
--
Regards,
Sylwester
--
Sylwester Nawrocki
Samsung Poland R&D Center
next prev parent reply other threads:[~2011-08-31 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0LQO00HOLZVZDW20@ms6.samsung.com>
2011-08-31 8:42 ` Add clkdev support to HSMMC Sylwester Nawrocki
2011-08-31 10:13 ` Thomas Abraham
2011-08-31 12:56 ` Sylwester Nawrocki [this message]
2011-08-31 13:13 ` Thomas Abraham
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=4E5E2F80.3010005@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=banajit.g@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.v@samsung.com \
--cc=rajeshwari.s@samsung.com \
--cc=thomas.abraham@linaro.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.