From: Wolfram Sang <w.sang@pengutronix.de>
To: Dragos Carp <dragos.carp@toptica.com>
Cc: spi-devel-general@lists.sourceforge.net,
David Brownell <dbrownell@users.sourceforge.net>,
linuxppc-dev@ozlabs.org
Subject: Re: [spi-devel-general] [PATCH] mpc52xx_psc_spi: enlarge clock range
Date: Thu, 17 Sep 2009 16:13:31 +0200 [thread overview]
Message-ID: <20090917141331.GA3169@pengutronix.de> (raw)
In-Reply-To: <4AB241FA.9090604@toptica.com>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
> I wasn't aware that MPC5200 differ from MPC5200B in this regard. I also
> couldn't find any MPC5200 user manual on Freescale's webpage.
Hmm, it was the first hit using a web search engine :)
http://www.freescale.com/files/microcontrollers/doc/user_guide/MPC5200UM.pdf?WT_TYPE=Users%20Guides&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation
> Is there a #define that I can use to distinguish between the two
> processor variants? Querying the PVR register is not a nice solution
I think you should have two different functions for calculation, one for 5200
and one for 5200B. During init query the device tree for 'fsl,mpc5200-psc-spi'
or 'fsl,mpc5200b-psc-spi' and make the driver use the proper function.
(BTW I haven't checked for further differences between 5200 and 5200B; there
may be more)
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-09-17 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AB0C706.5020601@toptica.com>
2009-09-16 20:48 ` [spi-devel-general] [PATCH] mpc52xx_psc_spi: enlarge clock range Wolfram Sang
2009-09-17 14:04 ` Dragos Carp
2009-09-17 14:13 ` Grant Likely
2009-09-17 14:13 ` Wolfram Sang [this message]
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=20090917141331.GA3169@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=dbrownell@users.sourceforge.net \
--cc=dragos.carp@toptica.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).