Hi all,
I have a strange problem on a self-developed MPC5200B system (more or less like the
Freescale Lite board). On that board, I use kernel 3.2.68 with my own
machine init file, which is almost the same as for Lite
(arch/powerpc/platforms/52xx/lite5200.c). Everything works just fine.
Hi Stephan:
Am 30.06.12 21:16 schrieb(en) Stephan Gatzka:
I have a problem running jffs2 on an MPC5200b board. I run kernel 3.4, but
older kernels like 3.1.5 are also affected. Every time I mount jffs2,
previously written content gets garbled.
The problem was nailed down to memcpy(fd-name,
Hi all,
I have a slightly off-topic question regarding the use of mpc52xx_lpbfifo_submit()
friends...
In struct mpc52xx_lpbfifo_request, the element 'data' (with address 'data_phys') is
apparently the chunk of data which is transferred through bestcomm, right? Dumb
question: has this chunk
Hi all,
sorry for a slightly off-topic question, but I hope someone here on the list
may be able to help me...
I have a strange problem with the psc uart of the mpc5200b, running 2.6.32.26
(still), with my baud rate divisor selection patch [1].
The uart runs at 115.2 kBaud with rtc/cts
Am 08.07.10 17:22 schrieb(en) Grant Likely:
Just out of curiousity, what configuration might cause a byte-wise alignment
not to work?
Can't remember the register configuration, but I worked on one project where
this was the case. In hindsight, it was probably a mis-configuration of the
Am 08.07.10 21:30 schrieb(en) Segher Boessenkool:
Actually, this is something which might need closer attention - and maybe some
support in the device tree indicating which read or write width a device can
accept?
There already is device-width; the drivers never should use any other access
Am 19.05.10 18:02 schrieb(en) Grant Likely:
That's http://git.secretlab.ca/?p=linux-2.6.git;a=shortlog, isn't it?
Hmmm, didn't find it there... :-/
Ugh... Stupid typing too fast. I meant to say, I *don't* think ben
has asked me to take...
Well this leaves a bit of a mess. I'll make sure
Am 06.05.10 20:06 schrieb(en) Grant Likely:
I think, though, the whole stuff has been discussed in depth in February, so
I do not understand why it's still pending as new. Grant, did we miss
something here?
I generally let subsystem maintainers pick up the device driver
patches for embedded
Am 06.05.10 00:09 schrieb(en) Ira W. Snyder:
Did this series get forgotten about? I don't see it in bjdook's next-i2c branch
or in benh's next branch.
It's not in Grant's 5xxx tree either - as it's specific for those processors, I think he
might be the responsible person. The patch is still
Hi Grant:
Am 27.04.10 20:28 schrieb(en) Albrecht Dreß:
MPC5121e Hardware Design Guide provides correct info according to my tests
using /16 and /10 prescaler. I've send a new patch with the fixed comments,
unfortunately forgot to mark it as v4, but it is threaded to your v.3a patch
Hi Sylvain:
Am 22.04.10 20:58 schrieb(en) Sylvain Lamontagne:
[snip]
1. Is it possible ?
Yes! I tried this with several kernel versions (currently 2.6.33), using the
option 'console=tty0'. Works just fine...
2. Do you have any idea how it can be achieve ?
Hmmm, iirc, I also saw the
Hi Josh:
Am 29.03.10 00:24 schrieb(en) Josh Triplett:
We have the MPC5200C rev of the board, not the MPC5200B rev which
Ummm - I didn't know that there is a 5200C available. The Freescale web site
only mentions the 5200 and the 5200B. Do you have any pointers to data
sheets/docs?
Thanks,
in mpc512x_psc_set_baudrate(). Any insight and
testing of the code (maybe Anatolij, when he's back from his vacation)
would be appreciated.
Tested on a custom 5200B based board, from 110 baud up to 3 MBaud, and with
both fsl,mpc5200b-psc-uart and fsl,mpc5200-psc-uart devices.
Signed-off-by: Albrecht Dreß
Am 26.03.10 23:59 schrieb(en) Josh Triplett:
[snip]
Any other ideas for things we could check to try to track down this problem?
Might your issue be related to this thread:
http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078757.html?
Cheers, Albrecht.
pgpEywOLv7gWI.pgp
Dear Grant:
Am 27.03.10 03:10 schrieb(en) Grant Likely:
Ping? I was looking at this tonight but it of course doesn't apply. Have you
gotten a chance to rebase this patch yet?
Thanks for the reminder - I sent Anatolij the rebased patch off-list (as I
didn't want to clutter the list again
Hi all,
not sure if this is the right place to ask: When I boot a custom 5200B (more
or less Lite-based) board with Linus' git tree (2.6.34-rc1-dirty), I always get
the following bug:
[1.110693] i2c /dev entries driver
[1.117285] mpc-i2c f0003d00.i2c: clock 375000 Hz (fdr=137)
[
Hi all,
I recently posted a patch which improves the baud rate calculation on the
mpc5200b. Following requests by Grant and Wolfram, I added changes which do
also affect the mpc512x.
Unfortunately, I don't have access to such a system, but IMHO the code (both
the old implementation and my
in mpc512x_psc_set_baudrate(). Any insight and
testing of the code would be appreciated.
Tested on a custom 5200B based board, from 110 baud up to 3 MBaud, and with
both fsl,mpc5200b-psc-uart and fsl,mpc5200-psc-uart devices.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Changes vs. v.2: Pick up
to 3 MBaud, and with both
fsl,mpc5200b-psc-uart and fsl,mpc5200-psc-uart devices.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Changes vs. v.1: include improvements suggested by Wolfram and Grant (thanks a
lot for your helpful input!!): drop getuartclk method and use the highest
MPC5200 does only
have a /32 prescaler which is detected only once and stored in a global. A
new chip-dependent method is used to set the divisor.
Tested on a custom 5200B based board, with up to 3 MBaud.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
--- linux-2.6.33/drivers/serial
Hi Roman:
Sorry for the long delay, I had to fix some other stuff first, before I could
launch the test... Here is just a short intermediate result.
Am 04.02.10 20:35 schrieb(en) Albrecht Dreß:
Actually, I forgot that I have to explicitly enable libata dma on the 5200b,
due to the known
Hi Joakim:
Am 18.02.10 18:14 schrieb(en) Joakim Tjernlund:
[snip]
static void mpc_i2c_fixup(struct mpc_i2c *i2c)
{
- writeccr(i2c, 0);
- udelay(30);
- writeccr(i2c, CCR_MEN);
- udelay(30);
- writeccr(i2c, CCR_MSTA | CCR_MTX);
- udelay(30);
-
in the device tree
- better description (I hope) of the changes.
I didn't split the changes in this file into three parts as recommended by
Grant, as they actually belong together (i.e. they address one single
problem, just in three places of one single source file).
Signed-off-by: Albrecht Dreß
Make the I2C adapter timeout configurable through a Device Tree property
which gives the timeout in microseconds.
Change vs. v.1: use fsl,timeout as property name (Thanks, Grant)
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
--- linux-2.6.32-orig/Documentation/powerpc/dts-bindings
Hi Roman:
Am 03.02.10 07:16 schrieb(en) Roman Fietze:
Sorry for the delay ... your mail got stuck in a Notes spam filter.
Never mind. I didn't know yet that I'm *such* a nasty guy... ;-)
Are you using MWDMA2 with the compact flash cards? What is the load on the
different (DMA) channels?
Am 25.01.10 05:06 schrieb(en) Ben Dooks:
On Fri, Jan 22, 2010 at 09:17:55PM +0100, Albrecht Dreß wrote:
Improve the recovery of the MPC5200B's I2C bus from errors like bus hangs.
This is very sparse comapred to the large comment below the --- line, maybe
some more description should
Am 25.01.10 08:55 schrieb(en) Wolfgang Grandegger:
Albrecht Dreß wrote:
Make the I2C adapter timeout configurable through a Device Tree property which
gives the timeout in microseconds.
My understanding is that software properties should not be defined via the
device tree. I think a sysfs
Hi Roman:
Am 16.12.09 12:37 schrieb(en) Roman Fietze:
The board is using the MPC5200B on a board derived from the old lite5200, but with the fixes for the MPC5200B. All tests are run using an ST940813AM hard drive with an ext2 and an ext3 of 10GB each, default mkfs options. The OS is Debian 4.0.
Improve the recovery of the MPC5200B's I2C bus from errors like bus
hangs.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
This patch introduces several improvements to the MPC5200B's I2C driver
as to improve the recovery from error conditions I encountered when
testing a custom board
Hi Grant:
Am 11.12.09 07:02 schrieb(en) Grant Likely:
The existing API (of_get_gpio()) doesn't operate on gpio-controller
nodes. It operates on a node that uses the gpio (has a 'gpios'
property as documented in
Documentation/powerpc/dts-bindings/gpio/gpio.txt).
Thanks a lot for that pointer
This set of patches merges the MPC5200 WDT into the GPT code, making it
functional again - currently, the MPC5200 GPT code blocks using the WDT.
Additionally, it defines a new OF property as to reserve and/or enable the
WDT during the boot process which may be a requirement for safety-related
Add the fsl,wdt-on-boot OF property as to reserve a GPT as WDT which may
be a requirement in safety-related (e.g. ISO/EN 61508) applications.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Change against v1: rename the new property.
Documentation/powerpc/dts-bindings/fsl/mpc5200.txt
Merge the WDT code into the GPT interface.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Change against v1: fully merge the wdt api into this file.
Note: The patch does also include the tiny GPT api changes from
http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-November/077647.html
Remove the old WDT implementation.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Change against v1: WDT stuff now fully merged into the file
arch/powerpc/platforms/52xx/mpc52xx_gpt.c.
Note: The file drivers/watchdog/mpc5200_wdt.c is now obsolete and should be
removed.
drivers
Hi Grant!
Am 12.11.09 20:06 schrieb(en) Grant Likely:
+The watchdog will respect the CONFIG_WATCHDOG_NOWAYOUT option.
I think it would be better to use a device tree property to enable up
NOWAYOUT. The static config isn't multiplatform-friendly. Thoughts?
I fully agree with you that this
Hi Wolfram:
Am 12.11.09 20:56 schrieb(en) Wolfram Sang:
Note: The file drivers/watchdog/mpc5200_wdt.c is now obsolete and should be
removed.
Ehrm, this is possible within a patch :)
Ummm, I tried that (removed the file from git locally), but apparently I'm too
dumb to find the proper
Add the wdt,on-boot OF property as to reserve a GPT as WDT which may be a
requirement in safety-related (e.g. ISO 61508) applications.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Documentation/powerpc/dts-bindings/fsl/mpc5200.txt | 15 ++-
1 files changed, 14
Merge the WDT code into the GPT interface.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
Notes:
The maximum timeout for a 5200 GPT @ 33 MHz clock is ~130 seconds. As this
exceeds the range of an int, some api's had to be changed to u64.
The WDT api is exported as to keep the WDT
Use the MPC5200 GPT api for the WDT which drastically simplifies this file.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
drivers/watchdog/mpc5200_wdt.c | 246 +++-
1 files changed, 65 insertions(+), 181 deletions(-)
diff --git a/drivers/watchdog
This set of patches merges the MPC5200 WDT into the GPT code, making it
functional again - currently, the MPC5200 GPT code blocks using the WDT.
Additionally, it defines a new OF property as to reserve and/or enable the
WDT during the boot process which may be a requirement for safety-related
Hi Grant:
Am 10.11.09 20:59 schrieb(en) Grant Likely:
On Tue, Nov 10, 2009 at 12:43 PM, Albrecht Dreß albrecht.dr...@arcor.de wrote:
Use the MPC5200 GPT api for the WDT which drastically simplifies this file.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
drivers/watchdog
See http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-May/072582.html.
Any chance to get this one into the tree? Grant?
Cheers, Albrecht.
Am 03.11.09 20:30 schrieb(en) Chris Friesen:
Forwarding to the ppc mailing list.
Chris
Original Message
Subject: [PATCH]
is more efficient than
explicitly loading it via bcom_load_image() after each
bcom_gen_bd_[rt]x_reset().
Except for a fixed tab vs. space formatting and the transfer format, there are
no diffierences to the initial attempt.
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
diff -uprN -X
Am 05.10.09 20:16 schrieb(en) Grant Likely:
Hmmm. I've not been comfortable with this change, but it took me a while to
put my finger on exactly why. In principle, I think it is a good idea.
However, I don't want to merge it without any in-tree users.
I could provide my modified microcode
Hi Wolfram:
Am 03.10.09 11:44 schrieb(en) Wolfram Sang:
you wrote your own microcode? :)
I modified the bcom_gen_bd_rx_task for a LPB peripheral as to perform
Endianess swapping during the transfer (works meanwhile :-).
Modifying the standard kernel code for testing seemed to be the
Am 03.10.09 16:40 schrieb(en) Wolfram Sang:
Sorry, I hardly know anything about the microcode. From what I know,
it shouldn't be much fun due to various bugs in the Bestcomm engine.
Ummm. That's not encouraging! :-/
Hey! No need for insults! ;)
Sorry, that wasn't my intention, but it's a
bcom_gen_bd_set_microcode() which is more efficient than explicitly
loading it via bcom_load_image() after each bcom_gen_bd_[rt]x_reset().
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
diff -uprN -X linux-2.6.30.3/Documentation/dontdiff
linux-2.6.30.3.orig/arch/powerpc/sysdev/bestcomm/gen_bd.c
linux
Hi John:
Cool stuff - Grant's original one also helped me a lot to get Bestcomm
running for me (I use it only for read dma)!
Am 29.09.09 22:43 schrieb(en) John Bonesio:
[snip]
+ * It may be worth experimenting with the ALARM value
to see if
+ * there is a performance impacit. However,
Am 25.09.09 14:15 schrieb(en) Jon Smirl:
No one has tried the Macraigor USB wiggler on the mpc5200 and
reported back if it works.
I'm working on a self-designed, roughly Lite5200B based board, and
first thought about buying this device. However, I tried to contact
their support several
Am 12.09.09 16:01 schrieb(en) Grant Likely:
I've actually got a better driver which exports an API for doing
local plus bus FIFO transfers. It's been posted to the mailing list
a couple of times. I'll cc: you the next time I post it (real soon
now).
Thanks a lot, that will be really
Hi all,
I have a MPC5200B based system with a 16-bit peripheral attached to the
Local Bus, and I am looking into possibilities to use BestComm for the
data transfer.
I found Grant Likely's cool 'mpc5200-localplus-test.c' driver which
demonstrates this using the 'gen_bd' driver, and which
-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
--- linux-2.6.30.3.orig/arch/powerpc/platforms/52xx/mpc52xx_gpt.c
2009-07-24 23:47:51.0 +0200
+++ linux-2.6.30.3/arch/powerpc/platforms/52xx/mpc52xx_gpt.c
2009-08-03 14:20:10.0 +0200
@@ -343,6 +343,14 @@
{
struct
Am 03.08.09 19:50 schrieb(en) Grant Likely:
Just about all mpc5200 device trees have the fsl,has-wdt property on
GPT0 even when it isn't used as a watchdog.
Sorry, I do not understand... The file
Documentation/powerpc/dts-bindings/fsl/mpc5200.txt says
snip
On the mpc5200 and 5200b, GPT0
limitations accessing chips in 16-bit mode through the local
bus, which is a lot easier and cleaner with this patch than with the
old one (of 05 June 09).
Acked-by: Albrecht Dreß albrecht.dr...@arcor.de
pgplqcxh10c73.pgp
Description: PGP signature
Am 19.06.09 19:06 schrieb(en) Lorenz Kolb:
Could you please try the following patch, I am quite sure that
checking for 4 was accidentially done within io.c instead of = 4
as if it's 4 we still can copy a 32-bit word. Some hardware might not
be happy about 8-bit accesses...
I submitted
Am 16.06.09 14:53 schrieb(en) Grant Likely:
I'm not happy about the use case though. It probably shouldn't
appear in this binding, or if it does it should be tagged as an
optional property.
I agree with you that the naming is really misleading - other devices
which are not mtd's may
Am 05.06.09 14:05 schrieb(en) Wolfram Sang:
Create an of-aware driver using the now exported generic functions
from plat-ram.c. Also add the documentation for the binding.
Partitions are not yet supported. Tested on a phyCORE-MPC5200B-IO.
Dumb question: what is the current status of this
Am 11.06.09 18:27 schrieb(en) Grant Likely:
+ *(u16 *)buf = *((volatile u16 *)(vdest - 1));
+ buf[1] = *((u8 *)src);
+ *((volatile u16 *)(vdest - 1)) = *(u16 *)buf;
what is the purpose of volatile here? If you need io barriers, then
use the
://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/072794.html
[2] http://article.gmane.org/gmane.linux.drivers.mtd/21521
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: David Woodhouse dw...@infradead.org
Cc: linuxppc-...@ozlabs.org
---
diff -u
linux
Am 08.06.09 18:35 schrieb(en) Wolfram Sang:
Question: why is bank-width even relevant for a RAM device?
The underlying map_ram-driver uses it once while erasing. The
question remains if this is really needed?
Am 06.06.09 18:16 schrieb(en) Albrecht Dreß:
At least if the RAM is attached
Am 06.06.09 18:05 schrieb(en) Grant Likely:
+ - bank-width : Width (in bytes) of the RAM bank.
Question: why is bank-width even relevant for a RAM device?
At least if the RAM is attached to the 5200's Local Plus Bus in 16-bit
mode, no byte write accesses are allowed (byte /reads/ work,
: Albrecht Dreß albrecht.dr...@arcor.de
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Ben Dooks ben-li...@fluff.org
Cc: David Woodhouse dw...@infradead.org
Cc: linuxppc-...@ozlabs.org
Cc: devicetree-disc...@ozlabs.org
Cc: linux-...@lists.infradead.org
These patches work great for me on a self
Am 03.06.09 16:36 schrieb(en) Kenneth Johansson:
On an e300 core using the lwzu/stwu is about 20% faster so at least
one core prefer that optimization.
Bingo. The '5200 on my test system has that core. So -mcpu=603e
should select this strategy!
Cheers, Albrecht.
pgpAeWzL3wfxw.pgp
Am 01.06.09 08:14 schrieb(en) Joakim Tjernlund:
.. not even 4.2.2 which is fairly modern will get it right. It breaks
very easy as gcc has never been any good at this type of
optimization. Sometimes small changes will make gcc unhappy and it
won't do the right optimization.
It's even
Hi Jocke:
Am 29.05.09 08:31 schrieb(en) Joakim Tjernlund:
No (and I wasn't aware of the PPC pre-inc vs. post-inc stuff) - I
just
I think this is true for most RISC based CPU's. It is a pity as
post ops are a lot more common. The do {} while(--chunks) is also
better. Basically the
Am 28.05.09 18:13 schrieb(en) Joakim Tjernlund:
hmm, these do look a bit unoptimal anyway. Any reason not to write
them something like below(written by me for uClibc long time ago).
You will have to add eieio()/sync
No (and I wasn't aware of the PPC pre-inc vs. post-inc stuff) - I just
Hi all:
Am 25.05.09 23:47 schrieb(en) Wolfram Sang:
A word or long copy of 0x0055aaff with U-Boot works fine, but a byte
copy filled the whole ram with 0x. The reason is apparently
that the chip is attached to the local bus in 16-bit mode, which is
incompatible with byte accesses.
This trivial patch changes memcpy_(to|from)io as to transfer as many
32-bit words as possible in 32-bit accesses (in the current solution,
the last 32-bit word was transferred as 4 byte accesses).
Signed-off-by: Albrecht Dreß albrecht.dr...@arcor.de
---
diff -urpN -X linux-2.6.29.1.orig
Hi Gary Wolfram:
Thanks for youre help, and sorry for the late reply - I've been on
vacation...
Am 20.05.09 21:59 schrieb(en) Gary Thomas:
Try to access this without using the cache.
Unfortunately, this is not cache related - I switched the dcache off
completely - same results.
Am
Am 20.05.09 16:23 schrieb(en) Gary Thomas:
In Linux, when I write the file to /dev/mtdx, the last dword of
each block is broken, e.g. when running dd if=pattern of=/dev/mtd5
bs=512 the dword's at offset 0x1fc, 0x3fc, ... are 0x
(instead of 0x0055aaff), if I use bs=1024 the dwords
Hi Wolfram!
Am 19.05.09 14:27 schrieb(en) Wolfram Sang:
I wrote such a driver (yet without partitioning support) and I am
trying to get it mainline, just didn't get any comments so far:
http://patchwork.ozlabs.org/patch/23557/
http://patchwork.ozlabs.org/patch/23556/
Thanks a lot, this is
Hi Grant:
Am 27.04.09 19:36 schrieb(en) Grant Likely:
For completeness use: compatible =
fsl,mpc5200b-lpb,fsl,mpc5200-lpb,simple-bus; Then it will work.
I doesn't. I had to add fsl,lpb, without no localbus nodes show up.
The file arch/powerpc/platforms/52xx/mpc52xx_common.c lists only
Hi all,
I have a question about the definition of the localbus on the Freescale
5200B (I'm testing with the Lite5200B board) with Kernel 2.6.29.1 which
I could not figure out with the docs and the list archives...
When I use 'compatible = fsl,mpc5200b-lpb;' in the dts file, the
localbus
Am 23.04.09 02:05 schrieb(en) Grant Likely:
http://patchwork.ozlabs.org/patch/24487/
That patch is already included in 2.6.29...
No, that's not the problem in this case. 2.6.29 networking is broken
for a lot of platforms, not just mpc5200. Use 2.6.29.1 instead.
...and with 2.6.29.1,
Hi all,
I have some probably dumb questions regarding the definition of i2c
slaves in the of device tree file...
My test system is a lite5200b board to which I attached two pca8575 io
expander chips at i2c addresses 0x20 and 0x21. Using the stock kernel
2.6.29, I added the driver from
75 matches
Mail list logo
