From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: samsung: add set_rate and round_rate callbacks for pll45xx
Date: Mon, 05 Aug 2013 11:38:48 -0700 [thread overview]
Message-ID: <20130805183848.5348.5070@quantum> (raw)
In-Reply-To: <CAKew6eVBtbS1qaaauGOOTj831m-KHK7gyOSTcNQHzvw_vKiTgQ@mail.gmail.com>
Quoting Yadwinder Singh Brar (2013-07-11 22:48:55)
> Sorry I missed to state a point in earlier reply..,
>
>
> >>> +#define PLL45XX_PMS(f, p, m, s) \
> >>> + { \
> >>> + .target_freq = f, \
> >>> + .pdiv = p, \
> >>> + .mdiv = m, \
> >>> + .sdiv = s, \
> >>> + }
> >>> +
> >>> enum pll46xx_type {
> >>> pll_4600,
> >>> pll_4650,
> >>
> >> Basically, I would prefer the way introduced by Yadwinder's and Vikas' patches
> >> to be used. We already discussed all the aspects during all the 7 versions of
> >> those patches and decided to go with that solution, so for the case of
> >> consistency, same should be used for remaining PLLs.
> >
> > Ok, but could we look at this once more. We could avoid duplication of
> > PLL tables if the lookup tables are kept generic. It would be nice to
> > get opinions from others as well on this.
> >
>
> The rationale behind using common enum type was to use common(generic) set
> of clk ops where ever it is possible, to avoid duplication of most of
> the code(which
> looks mostly common with many PLLs). For example its done for 35xx & 25xx
> and 36xx & 26xx PLLs in that series.
Was there ever a consensus reached on the pll45xx round_rate & set_rate
implementation?
Regards,
Mike
>
> Regards,
> Yadwinder
next prev parent reply other threads:[~2013-08-05 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:27 [PATCH] clk: samsung: add set_rate and round_rate callbacks for pll45xx Thomas Abraham
2013-07-11 10:19 ` Tomasz Figa
2013-07-11 15:19 ` Thomas Abraham
2013-07-12 5:27 ` Yadwinder Singh Brar
2013-07-12 5:48 ` Yadwinder Singh Brar
2013-08-05 18:38 ` Mike Turquette [this message]
2013-07-11 10:44 ` Yadwinder Singh Brar
2013-07-11 15:24 ` Thomas Abraham
2013-07-12 5:11 ` Yadwinder Singh Brar
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=20130805183848.5348.5070@quantum \
--to=mturquette@linaro.org \
--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).