From: Jon Smirl <jonsmirl@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: PSC clock divider
Date: Fri, 7 Aug 2009 12:34:19 -0400 [thread overview]
Message-ID: <9e4733910908070934se43b2a9lfe72e89e0e247ea3@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40908070915x7e04cbb8ofccd106230d5f76c@mail.gmail.com>
On Fri, Aug 7, 2009 at 12:15 PM, Grant Likely<grant.likely@secretlab.ca> wrote:
>> Should I modify mpc52xx_set_psc_clkdiv() to take in a frequency and
>> them move this code into mpc52xx_common.c? That allows the sysclk
>> parameter to be eliminated for SPI.
>
> Yes, please do.
Can mpc5xxx_clocks.c be eliminated and this function:
mpc5xxx_get_bus_frequency(struct device_node *node)
be moved into mpc52cc_common.c?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2009-08-07 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 16:03 PSC clock divider Jon Smirl
2009-08-07 16:15 ` Grant Likely
2009-08-07 16:34 ` Jon Smirl [this message]
2009-08-07 18:29 ` Grant Likely
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=9e4733910908070934se43b2a9lfe72e89e0e247ea3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=grant.likely@secretlab.ca \
/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).