From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Domen Puncer" <domen.puncer@telargo.com>
Cc: david-b@pacbell.net, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] clk for mpc52xx: use psc_mclk's in spi driver
Date: Sun, 14 Oct 2007 16:42:45 -0600 [thread overview]
Message-ID: <fa686aa40710141542w552eacet7ba13e8e251e2285@mail.gmail.com> (raw)
In-Reply-To: <20071014081027.GJ3000@nd47.coderock.org>
On 10/14/07, Domen Puncer <domen.puncer@telargo.com> wrote:
> Use clocks subsystem in spi driver.
I don't understand the advantage of this approach. Is the current code broken?
I agree that abstraction is good; but in this case it seems these two
patches add a lot of code for a very simple calculation. Also, there
is exactly 2 chips that use these devices, the mpc5200 and the
mpc5200b, and they are both wired up in exactly the same way. I'm
inclined to believe that splitting of reading of the CDM into a
separate driver (or at least using the clk infrastructure) is over the
edge of diminishing returns. However, I could be convinced that
having a utility function for setting the PSC clock rate is a useful
thing, but until arch/ppc goes away, you should support it in both
arch/ppc and arch/powerpc.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-14 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 8:08 [PATCH 0/2] clk for mpc52xx Domen Puncer
2007-10-14 8:09 ` [PATCH 1/2] clk for mpc52xx: platform part Domen Puncer
2007-10-14 13:33 ` Stephen Rothwell
2007-10-14 8:10 ` [PATCH 2/2] clk for mpc52xx: use psc_mclk's in spi driver Domen Puncer
2007-10-14 22:42 ` Grant Likely [this message]
2007-10-15 5:16 ` Domen Puncer
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=fa686aa40710141542w552eacet7ba13e8e251e2285@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=david-b@pacbell.net \
--cc=domen.puncer@telargo.com \
--cc=linuxppc-dev@ozlabs.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).