This patch enables or updates support for the CC770 and AN82527
CAN controller on the TQM8548 and TQM8xx boards.
CC: devicetree-disc...@lists.ozlabs.org
CC: linuxppc-...@ozlabs.org
CC: Kumar Gala ga...@kernel.crashing.org
Signed-off-by: Wolfgang Grandegger w...@grandegger.com
---
This driver works with both, static platform data and device tree
bindings. It has been tested on a TQM855L board with two AN82527
CAN controllers on the local bus.
CC: devicetree-disc...@lists.ozlabs.org
CC: linuxppc-...@ozlabs.org
CC: Kumar Gala ga...@kernel.crashing.org
Signed-off-by: Wolfgang
Hi,
I have a P2020 CPU (powerpc) and I compiled it with two different defconfigs.
The first one is a SMP, 2 cores, launched with the nosmp kernel
parameter, the other one is an UP kernel.
My driver behaviour is not the same whether launching one or the
other. It is hard to explain more
On Mon, Nov 28, 2011 at 02:11:11PM +1100, David Gibson wrote:
[snip]
On Wed, Oct 12, 2011 at 11:09:48PM +0530, K.Prasad wrote:
+ if (bp) {
+ attr = bp-attr;
+ attr.bp_addr = (unsigned long)bp_info-addr
~HW_BREAKPOINT_ALIGN;
+
Benjamin Herrenschmidt wrote:
On Wed, 2011-11-30 at 19:06 +0800, tiejun.chen wrote:
- Copy the exception frame we're about to unwind to just -below- the
new r1 value we want to write to. Then perform the write, and change
r1 to point to that copy of the frame.
- Branch to restore: which
On Thu, Dec 1, 2011 at 12:39 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
Hi Josh !
I was helping Tony with some of the Currituck stuff when I noticed an
oddity...
So we have various SoC config symbols such as 440EP, 460SX, etc...
that in turn select various bits pieces that
On Dec 1, 2011, at 3:57 AM, Jean-Michel Hautbois wrote:
Hi,
I have a P2020 CPU (powerpc) and I compiled it with two different defconfigs.
The first one is a SMP, 2 cores, launched with the nosmp kernel
parameter, the other one is an UP kernel.
My driver behaviour is not the same whether
2011/12/1 Kumar Gala ga...@kernel.crashing.org:
On Dec 1, 2011, at 3:57 AM, Jean-Michel Hautbois wrote:
Hi,
I have a P2020 CPU (powerpc) and I compiled it with two different defconfigs.
The first one is a SMP, 2 cores, launched with the nosmp kernel
parameter, the other one is an UP
On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Any idea on how to debug this ? I am using a 2.6.35 kernel.
There are a ton of Kconfig options for debugging various locking bugs.
Try turning them on.
--
Timur Tabi
Linux kernel developer at Freescale
2011/12/1 Tabi Timur-B04825 b04...@freescale.com:
On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Any idea on how to debug this ? I am using a 2.6.35 kernel.
There are a ton of Kconfig options for debugging various locking bugs.
Try turning them on.
And
An I2C device tree node can contain a 'cell-index' property that can be
used to enumerate the I2C devices. If such a property exists, use it
to specify the I2C adapter number.
This feature is necessary for the Freescale PowerPC audio drivers (e.g.
on the P1022DS). The machine driver needs to
2011/12/1 Jean-Michel Hautbois jhautb...@gmail.com:
2011/12/1 Tabi Timur-B04825 b04...@freescale.com:
On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Any idea on how to debug this ? I am using a 2.6.35 kernel.
There are a ton of Kconfig options for debugging
On 12/01/2011 11:33 AM, Timur Tabi wrote:
An I2C device tree node can contain a 'cell-index' property that can be
used to enumerate the I2C devices. If such a property exists, use it
to specify the I2C adapter number.
Didn't we decide a long time ago that this was a bad idea?
This feature
Fix some PS3 repository.c build warnings when DEBUG is
defined. Also change most pr_debug calls to pr_devel calls.
Fixes warnings like these:
format '%lx' expects type 'long unsigned int', but argument 7 has type 'u64'
Signed-off-by: Geoff Levand ge...@infradead.org
---
Hi Ben,
I rebased my
On Dec 1, 2011, at 11:52 AM, Jean-Michel Hautbois wrote:
2011/12/1 Jean-Michel Hautbois jhautb...@gmail.com:
2011/12/1 Tabi Timur-B04825 b04...@freescale.com:
On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Any idea on how to debug this ? I am using a
2011/12/1 Kumar Gala ga...@kernel.crashing.org:
On Dec 1, 2011, at 11:52 AM, Jean-Michel Hautbois wrote:
2011/12/1 Jean-Michel Hautbois jhautb...@gmail.com:
2011/12/1 Tabi Timur-B04825 b04...@freescale.com:
On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
jhautb...@gmail.com wrote:
Scott Wood wrote:
On 12/01/2011 11:33 AM, Timur Tabi wrote:
An I2C device tree node can contain a 'cell-index' property that can be
used to enumerate the I2C devices. If such a property exists, use it
to specify the I2C adapter number.
Didn't we decide a long time ago that this was a bad
On 12/01/2011 02:54 PM, Timur Tabi wrote:
Scott Wood wrote:
On 12/01/2011 11:33 AM, Timur Tabi wrote:
An I2C device tree node can contain a 'cell-index' property that can be
used to enumerate the I2C devices. If such a property exists, use it
to specify the I2C adapter number.
Didn't we
On Thu, 2011-12-01 at 18:44 +0800, tiejun.chen wrote:
Do you mean we should push the original pt_regs (or that whole exception
stack)
downwards the location the new r1 point? Then its safe to perform this real
emulated stw instruction. At last we will reroute r1 to that copied exception
On Thu, 2011-12-01 at 06:44 -0500, Josh Boyer wrote:
However, the entry for ppc44x_simple doesn't select any of these,
meaning for example, AFAIK, that you don't get EMAC4 etc... I'm
surprised things work at all !
What am I missing ?
CONFIG_PPC44x_SIMPLE is selected by the board
Scott Wood wrote:
How is this going to interact with other i2c buses (e.g. on a board
FPGA) that might have a conflicting static numbering scheme? Have you
ensured that no dynamic bus registrations (e.g. an i2c bus on a PCI
device) can happen before the static SoC i2c buses are added?
On 12/01/2011 03:46 PM, Timur Tabi wrote:
Scott Wood wrote:
How is this going to interact with other i2c buses (e.g. on a board
FPGA) that might have a conflicting static numbering scheme? Have you
ensured that no dynamic bus registrations (e.g. an i2c bus on a PCI
device) can happen
On Thu, Dec 1, 2011 at 2:52 PM, Scott Wood scottw...@freescale.com wrote:
On 12/01/2011 03:46 PM, Timur Tabi wrote:
Scott Wood wrote:
How is this going to interact with other i2c buses (e.g. on a board
FPGA) that might have a conflicting static numbering scheme? Have you
ensured that no
Grant Likely wrote:
It is better to walk the list of i2c adapters and look for one that
has the matching node pointer. It really isn't an expensive operation
to do it that way.
That's what I was thinking. I can't figure out how to walk the list, though.
i2c_get_adapter() takes an adapter
Scott Wood wrote:
Ideally we would have a field in struct device_node that points to
struct device.
I don't think there's a single place in the code where the connection between
the device and device_node is made. In fact, I think dev-of_node needs to be
manually initialized by the driver
On 12/01/2011 03:59 PM, Timur Tabi wrote:
Scott Wood wrote:
Ideally we would have a field in struct device_node that points to
struct device.
I don't think there's a single place in the code where the connection
between the device and device_node is made. In fact, I think
dev-of_node
Scott Wood wrote:
Does of_find_i2c_device_by_node() do what you want?
Yeah, that'll work. I wasn't thinking about looking for an i2c device. Thanks.
--
Timur Tabi
Linux kernel developer at Freescale
___
Linuxppc-dev mailing list
+#define mfdcrx(rn) \
+ ({ \
+ unsigned long rval; \
+ asm volatile(mfdcrx %0,%1 : =r(rval) : g(rn)); \
+ rval; \
+ })
g is never correct on PowerPC, you want r here. You can write
this as a static inline btw, you only need the #define
The normal arch hook into the 8250 serial world is via passing
in a plat_serial8250_port struct. However, this struct does
not have a bugs field, so there is no way to have the arch
code pass in info about known uart issues.
Add a bug field to the plat_serial8250_port struct, so that the
arch
This is a respin of an earlier patch[1] that enabled a workaround
via Kconfig for an errata issue when using BRK on FSL 16550 UARTs.
In this version, the 8250 specific bug field is moved to the generic
uart_port struct, since hardware bugs aren't the unique domain of
just the 8250 class of
There is a struct uart_8250_port that is private to 8250.c
itself, and it had a bugs field. But there is no reason to
assume that hardware bugs are unique to 8250 type UARTS.
Make the bugs field part of the globally visible struct
uart_port and remove the 8250 specific one.
The value in doing
Sending a break on the SOC UARTs found in some MPC83xx/85xx/86xx
chips seems to cause a short lived IRQ storm (/proc/interrupts
typically shows somewhere between 300 and 1500 events). Unfortunately
this renders SysRQ over the serial console completely inoperable.
The suggested workaround in the
On 12/01/2011 05:47 PM, Paul Gortmaker wrote:
diff --git a/include/linux/serial_8250.h b/include/linux/serial_8250.h
index 8c660af..b0f4042 100644
--- a/include/linux/serial_8250.h
+++ b/include/linux/serial_8250.h
@@ -18,6 +18,11 @@
#define UART_BUG_TXEN(1 1)/* buggy TX
On 11-12-01 06:51 PM, Scott Wood wrote:
On 12/01/2011 05:47 PM, Paul Gortmaker wrote:
diff --git a/include/linux/serial_8250.h b/include/linux/serial_8250.h
index 8c660af..b0f4042 100644
--- a/include/linux/serial_8250.h
+++ b/include/linux/serial_8250.h
@@ -18,6 +18,11 @@
#define
From aebed2e9fb9fba7dd0a34595780b828d7a545ba2 Mon Sep 17 00:00:00 2001
From: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
Date: Mon, 29 Aug 2011 14:12:08 -0700
Subject: [PATCH 1/1][v2] Enable CONFIG_STRICT_DEVMEM support for Powerpc.
As described in the help text in the patch, this token
On Dec 1, 2011, at 6:05 PM, Paul Gortmaker wrote:
On 11-12-01 06:51 PM, Scott Wood wrote:
On 12/01/2011 05:47 PM, Paul Gortmaker wrote:
diff --git a/include/linux/serial_8250.h b/include/linux/serial_8250.h
index 8c660af..b0f4042 100644
--- a/include/linux/serial_8250.h
+++
On Mon, Nov 28, 2011 at 3:02 PM, Kumar Gala ga...@kernel.crashing.org wrote:
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
* Need to fixup the commit message
I had this written when I was thinking of re-sending the dts
with the other three, that is before I realized the dts patch
Make the bugs field part of the globally visible struct
uart_port and remove the 8250 specific one.
Except all the bits in it are 8250 specific things or names that are
meaningless in generic form - no. I also don't want to encourage flags
and bug bits. We already have too many and its making
@@ -1553,7 +1554,15 @@ static void serial8250_handle_port(struct
uart_8250_port *up)
spin_lock_irqsave(up-port.lock, flags);
- status = serial_inp(up, UART_LSR);
+ /* Workaround for IRQ storm errata on break with Freescale
16550 */
+ if (UART_BUG_FSLBK up-port.bugs
On Thu, 2011-12-01 at 16:11 -0800, Sukadev Bhattiprolu wrote:
From aebed2e9fb9fba7dd0a34595780b828d7a545ba2 Mon Sep 17 00:00:00 2001
From: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
Date: Mon, 29 Aug 2011 14:12:08 -0700
Subject: [PATCH 1/1][v2] Enable CONFIG_STRICT_DEVMEM support for
And an additional comment regarding the rtas bit:
#ifdef CONFIG_PPC_SMLPAR
void arch_free_page(struct page *page, int order);
diff --git a/arch/powerpc/kernel/rtas.c b/arch/powerpc/kernel/rtas.c
index d5ca823..07cf2cf 100644
--- a/arch/powerpc/kernel/rtas.c
+++
On Thu, Dec 1, 2011 at 7:51 PM, Alan Cox a...@linux.intel.com wrote:
Make the bugs field part of the globally visible struct
uart_port and remove the 8250 specific one.
Except all the bits in it are 8250 specific things or names that are
meaningless in generic form - no. I also don't want to
On Thu, 2011-12-01 at 12:46 +1100, Anton Blanchard wrote:
When issuing a system reset we almost always oops in the oops_to_nvram
code because multiple CPUs are using the deflate work area. Add a
spinlock to protect it.
To play it safe I'm using trylock to avoid locking up if the NVRAM
code
On Thu, Dec 1, 2011 at 7:57 PM, Alan Cox a...@linux.intel.com wrote:
@@ -1553,7 +1554,15 @@ static void serial8250_handle_port(struct
uart_8250_port *up)
spin_lock_irqsave(up-port.lock, flags);
- status = serial_inp(up, UART_LSR);
+ /* Workaround for IRQ storm errata on break
Ben,
I fixed the 3 issues that Paul and Michael reported and I can provide them
to you two different ways, however you would prefer. I can also send the
patches via email if that's more convenient.
Option 1: Squashed into the the original patches for bisectability:
Hi
I just found that the 'next' branch you mentioned have problem to boot up.
I test it in p1022ds and p1010rdb boards and the result are both the same.
Note that for p1022ds I use make p1022ds.dtb to make the dtb file(36bit) with
36bit-uboot.
And for p1010rdb I use all 32bit image.
The problem
On Thu, 2011-12-01 at 19:48 -0600, Moffett, Kyle D wrote:
Ben,
I fixed the 3 issues that Paul and Michael reported and I can provide them
to you two different ways, however you would prefer. I can also send the
patches via email if that's more convenient.
Option 1: Squashed into the the
Benjamin Herrenschmidt [b...@kernel.crashing.org] wrote:
| And an additional comment regarding the rtas bit:
| +int devmem_is_allowed(unsigned long pfn)
| +{
| + if (iomem_is_exclusive(pfn PAGE_SHIFT))
| + return 0;
| + if (!page_is_ram(pfn))
| + return 1;
| + if
Hi Iris,
I'm convinced that smp_rmb() is needed when removing the spinlock. As noted,
Documentation/memory-barriers.txt says that stores on one CPU can be
observed by another CPU in a different order.
Previously, there was an UNLOCK (in fsl_dma_tx_submit) followed by a LOCK (in
fsl_tx_status).
Jia Hongtao-B38951 wrote:
Hi
I just found that the 'next' branch you mentioned have problem to boot up.
I test it in p1022ds and p1010rdb boards and the result are both the same.
Note that for p1022ds I use make p1022ds.dtb to make the dtb file(36bit)
with 36bit-uboot.
And for p1010rdb I
On Dec 1, 2011, at 8:21 PM, Jia Hongtao-B38951 wrote:
Hi
I just found that the 'next' branch you mentioned have problem to boot up.
I test it in p1022ds and p1010rdb boards and the result are both the same.
Note that for p1022ds I use make p1022ds.dtb to make the dtb file(36bit)
with
On Dec 1, 2011, at 9:55 PM, Tabi Timur-B04825 wrote:
Jia Hongtao-B38951 wrote:
Hi
I just found that the 'next' branch you mentioned have problem to boot up.
I test it in p1022ds and p1010rdb boards and the result are both the same.
Note that for p1022ds I use make p1022ds.dtb to make the
So I've had one of these for a while and it looks like the vendor never
bothered submitting the support upstream.
This adds it using ppc40x_simple and provides a device-tree.
There are some changes to the boot wrapper because the way u-boot works
on this thing, it seems to expect a multipart
Hi,
On Thu, Dec 1, 2011 at 9:35 PM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
arch/powerpc/boot/dts/obs600.dts | 314
It'd be nice to have dtsi files for the SoCs, there's a lot of boiler
plate in there. That shouldn't hold up this
Yes, both v3.2-rc3 and v3.2-rc4 in Linus's tree have the same issue.
- Hongtao.
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Friday, December 02, 2011 12:12 PM
To: Jia Hongtao-B38951
Cc: LinuxPPC-dev list; Li Yang-R58472
Subject: Re: [linuxppc-release]
The MDIO driver has been changed so that it no longer supports
scanning the MDIO bus for a free address for the TBI PHY. This
feature was fragile, and required scanning the bus before the bus
was fully up and registered. The intended way for FSL devices to
specify the TBI PHY's address is via a
This reverts commit c3e072f8a6c5625028531c40ec65f7e301531be2.
The TBI PHY Address must always be set to something sensible.
If not, the value currently in the register may interfere
with MDIO transactions to that address. The architected
solution is to have a TBI node in the device tree, which
On Dec 2, 2011, at 1:05 AM, Andy Fleming wrote:
The MDIO driver has been changed so that it no longer supports
scanning the MDIO bus for a free address for the TBI PHY. This
feature was fragile, and required scanning the bus before the bus
was fully up and registered. The intended way for
58 matches
Mail list logo
