Re: [PATCH 3/4 v5] video, sm501: add OF binding to support SM501
Hello Heiko Schocher wrote: - add binding to OF, compatible name smi,sm501 Signed-off-by: Heiko Schocher h...@denx.de cc: linux-fb...@vger.kernel.org cc: devicetree-disc...@ozlabs.org cc: Ben Dooks b...@simtec.co.uk cc: Vincent Sanders vi...@simtec.co.uk cc: Samuel Ortiz sa...@linux.intel.com cc: linux-ker...@vger.kernel.org cc: Randy Dunlap rdun...@xenotime.net cc: Paul Mundt let...@linux-sh.org --- - changes since v1: add Ben Dooks, Vincent Sanders and Samuel Ortiz to cc, as suggested from Paul Mundt. - changes since v2: add comments from Randy Dunlap: - move parameter documentation to Documentation/fb/sm501.txt - changes since v3: - rebased against v2.6.38-rc2 - split in 3 patches - of support patch - get rid of #if defined(CONFIG_PPC_MPC52xx) usage hide this in DTS, as Paul suggested. - i/o routine patch - edid support patch - changes since v4 replace remaining CONFIG_PPC_MPC52xx with CONFIG_OF, as it is no longer MPC52xx only. - changes since v5 free edid_data after its usage, as it is no longer needed, suggested from Paul Mundt. Also fall back to default if kmemdup(edid_data) fails. ./scripts/checkpatch.pl 0003-video-sm501-add-OF-binding-to-support-SM501.patch total: 0 errors, 0 warnings, 132 lines checked 0003-video-sm501-add-OF-binding-to-support-SM501.patch has no obvious style problems and is ready for submission. Documentation/powerpc/dts-bindings/sm501.txt | 34 + drivers/mfd/sm501.c |9 +- drivers/video/sm501fb.c | 42 -- 3 files changed, 81 insertions(+), 4 deletions(-) create mode 100644 Documentation/powerpc/dts-bindings/sm501.txt This patchset is pending know for a while. I got Acked by from Samuel Ortiz for the mfd part, see here: http://www.spinics.net/lists/linux-fbdev/msg02550.html http://linux.derkeiler.com/Mailing-Lists/Kernel/2011-01/msg11798.html and for the DTS part from Benjamin Herrenschmidt: http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-February/088279.html Are there some more issues? bye, Heiko -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden
On Tue, Mar 15, 2011 at 2:13 AM, Mahesh J Salgaonkar mah...@linux.vnet.ibm.com wrote: During free we do free all of them including RMO region. But since the rtas region is always on top of RMO, crashkernel memory overlaps rtas region and we endup freeing that even, which is causing the crash. Okay, but with this patch applied, we will just ignore rtas region, right? Thus, when I echo 0 to free all the 128M crashkernel memory, the final result will be 32M left, which means crash_size will still show 32M. This looks odd. How about skipping the 32M as a whole? I mean once the region being freed has overlap with this rtas region, skip the whole rtas region, and let crash_size show 0? Thanks. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH v3 1/6] powerpc: Move udbg_early_init() after early_init_devtree()
On Wed, Feb 09, 2011 at 05:08:08PM -0600, Dave Kleikamp wrote:
so that it can use information from the device tree.
Signed-off-by: Dave Kleikamp sha...@linux.vnet.ibm.com
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Josh Boyer jwbo...@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
---
Ben, you want this patch dropped, right?
josh
arch/powerpc/kernel/setup_32.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/setup_32.c b/arch/powerpc/kernel/setup_32.c
index 1d2fbc9..d1ca976 100644
--- a/arch/powerpc/kernel/setup_32.c
+++ b/arch/powerpc/kernel/setup_32.c
@@ -120,12 +120,12 @@ notrace void __init machine_init(unsigned long dt_ptr)
{
lockdep_init();
- /* Enable early debugging if any specified (see udbg.h) */
- udbg_early_init();
-
/* Do some early initialization based on the flat device tree */
early_init_devtree(__va(dt_ptr));
+ /* Enable early debugging if any specified (see udbg.h) */
+ udbg_early_init();
+
probe_machine();
setup_kdump_trampoline();
--
1.7.3.4
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Please pull 'next' branch of 4xx tree
On Tue, Feb 15, 2011 at 09:54:45AM -0500, Josh Boyer wrote: Hi Ben, Please pull the 'next' branch of the 4xx tree. These commits have been sitting there for a while and I wanted to get them into your branch before tackling the latest round of 476 stuff from Shaggy. Ben, I don't see any of these in your -next branch. Did you ever pull this? josh The following changes since commit 5d7d8072edc11080a7cf6cc37c9f4e61ca1e93c9: powerpc/pseries: Fix build of topology stuff without CONFIG_NUMA (2011-01-12 10:56:29 +1100) are available in the git repository at: ssh://master.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git next Dave Kleikamp (2): powerpc/476: define specific cpu table entry DD2 core powerpc/476: Workaround for PLB6 hang Rupjyoti Sarmah (1): powerpc/44x: PHY fixup for USB on canyonlands board Tirumala Marri (1): powerpc/44x: Add USB DWC DTS entry to Canyonlands board arch/powerpc/boot/dts/canyonlands.dts | 24 + arch/powerpc/include/asm/cputable.h|3 +- arch/powerpc/kernel/cputable.c | 22 - arch/powerpc/mm/tlb_nohash_low.S | 35 +++ arch/powerpc/platforms/44x/44x.h |4 + arch/powerpc/platforms/44x/Kconfig |1 - arch/powerpc/platforms/44x/Makefile|1 + arch/powerpc/platforms/44x/canyonlands.c | 134 arch/powerpc/platforms/44x/ppc44x_simple.c |1 - 9 files changed, 218 insertions(+), 7 deletions(-) create mode 100644 arch/powerpc/platforms/44x/canyonlands.c ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] powerpc/85xx: Fix writing to spin table 'cpu-release-addr' on ppc64e
On Mar 5, 2011, at 3:05 PM, Kumar Gala wrote: From: Kumar Gala kumar.g...@freescale.com If the spin table is located in the linear mapping (which can happen if we have 4G or more of memory) we need to access the spin table via a cacheable coherent mapping like we do on ppc32 (and do explicit cache flush). See the following commit for the ppc32 version of this issue: commit d1d47ec6e62ab08d2ebb925fd9203abfad3adfbf Author: Peter Tyser pty...@xes-inc.com Date: Fri Dec 18 16:50:37 2009 -0600 powerpc/85xx: Fix SMP when cpu-release-addr is in lowmem Signed-off-by: Kumar Gala ga...@kernel.crashing.org --- arch/powerpc/platforms/85xx/smp.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] ppc, 83xx: rename and update kmeter1
On Mar 11, 2011, at 1:02 AM, Holger Brunck wrote:
Beside the MPC 8360 based board kmeter1 other km83xx boards
from keymile will follow. Therefore the board specific naming
kmeter1 for functions and files were replaced with km83xx.
Additionally some updates were made:
- update defconfig for 2.6.38
- rework flash partitioning in dts file
- add gpio controller for qe_pio_c in dts
Signed-off-by: Holger Brunck holger.bru...@keymile.com
Acked-by: Heiko Schocher h...@denx.de
CC: Benjamin Herrenschmidt b...@kernel.crashing.org
CC: Kumar Gala ga...@kernel.crashing.org
CC: Heiko Schocher h...@denx.de
---
arch/powerpc/boot/dts/kmeter1.dts | 69 +++-
arch/powerpc/configs/83xx/kmeter1_defconfig|7 +--
arch/powerpc/platforms/83xx/Makefile |2 +-
.../powerpc/platforms/83xx/{kmeter1.c = km83xx.c} | 46 +
4 files changed, 71 insertions(+), 53 deletions(-)
rename arch/powerpc/platforms/83xx/{kmeter1.c = km83xx.c} (80%)
applied
- k
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] ppc, 82xx: rename and update mgcoge board support
On Mar 10, 2011, at 5:52 AM, Holger Brunck wrote:
The mgcoge board from keymile is now base for some other
similar boards. Therefore the board specific name mgcoge
was renamed to a generic name km82xx. Additionally some
enhancements were made:
- rework partition table in dts file
- add cpm2_pio_c gpio controller in dts file
- update defconfig
- add pin description for SCC1
- add pin description and configuration for USB
Signed-off-by: Holger Brunck holger.bru...@keymile.com
Acked-by: Heiko Schocher h...@denx.de
CC: Benjamin Herrenschmidt b...@kernel.crashing.org
CC: Kumar Gala ga...@kernel.crashing.org
CC: Heiko Schocher h...@denx.de
---
arch/powerpc/boot/dts/mgcoge.dts | 47 ---
arch/powerpc/configs/mgcoge_defconfig |9 +---
arch/powerpc/platforms/82xx/Makefile |2 +-
arch/powerpc/platforms/82xx/{mgcoge.c = km82xx.c} | 62 ++--
4 files changed, 72 insertions(+), 48 deletions(-)
rename arch/powerpc/platforms/82xx/{mgcoge.c = km82xx.c} (69%)
applied
- k
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] e500: Erratum cpu a005 workaround
On Jan 25, 2011, at 12:02 AM, Liu Yu wrote: This errata can occur if a single-precision floating-point, double-precision floating-point or vector floating-point instruction on a mispredicted branch path signals one of the floating-point data interrupts which are enabled by the SPEFSCR (FINVE, FDBZE, FUNFE or FOVFE bits). This interrupt must be recorded in a one-cycle window when the misprediction is resolved. If this extremely rare event should occur, the result could be: The SPE Data Exception from the mispredicted path may be reported erroneously if a single-precision floating-point, double-precision floating-point or vector floating-point instruction is the second instruction on the correct branch path. According to errata description, some efp instructions which are not supposed to trigger SPE exceptions can trigger the exceptions in this case. However, as we haven't emulated these instructions here, a signal will send to userspace, and userspace application would exit. This patch re-issue the efp instruction that we haven't emulated, so that hardware can properly execute it again if this case happen. Signed-off-by: Liu Yu yu@freescale.com --- This is an erratum workaround patch. It would be better if the patch can go into 2.6.38. arch/powerpc/include/asm/reg.h |2 + arch/powerpc/math-emu/math_efp.c | 53 +- 2 files changed, 54 insertions(+), 1 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] ppc, 8xx: remove obsolete mgsuvd board
On Jan 13, 2011, at 6:11 AM, Holger Brunck wrote: The MPC852 based mgsuvd board from Keymile was initially ported, but later on not developed further. This patch removes the respective files to decrease merging conflicts and unneeded maintenance. Signed-off-by: Holger Brunck holger.bru...@keymile.com Acked-by: Heiko Schocherh...@denx.de Cc: Vitaly Bordug v...@kernel.crashing.org Cc: Marcelo Tosatti marc...@kvack.org --- arch/powerpc/boot/dts/mgsuvd.dts | 163 - arch/powerpc/configs/mgsuvd_defconfig | 81 arch/powerpc/platforms/8xx/Kconfig|6 - arch/powerpc/platforms/8xx/Makefile |1 - arch/powerpc/platforms/8xx/mgsuvd.c | 92 -- 5 files changed, 0 insertions(+), 343 deletions(-) delete mode 100644 arch/powerpc/boot/dts/mgsuvd.dts delete mode 100644 arch/powerpc/configs/mgsuvd_defconfig delete mode 100644 arch/powerpc/platforms/8xx/mgsuvd.c applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 2/2] dts: Update sata controller compatible for p1022ds board
On Jan 19, 2011, at 3:07 AM, Xulei wrote: Update p1022 sata compatible to fsl,p1022-sata, fsl,pq-sata-v2. p1022ds sata controller is v2 version comparing previous FSL sata controller, for example, mpc8536. Signed-off-by: Lei Xu b33...@freescale.com Signed-off-by: Roy Zang tie-fei.z...@freescale.com --- arch/powerpc/boot/dts/p1022ds.dts |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
On Feb 8, 2011, at 5:39 PM, Timur Tabi wrote: Improve the status messages that are displayed during some operations of the PowerPC watchdog timer driver. When the watchdog is enabled, the timeout is displayed as a number of seconds, instead of an obscure period. The period is the position of a bit in a 64-bit timer register. The higher the value, the quicker the watchdog timeout occurs. Some people chose a high period value for the timer and get confused as to why the board resets within a few seconds. Messages displayed during open and close are now debug messages, so that they don't clutter the console by default. Finally, printk() is replaced with the pr_xxx() equivalent. Signed-off-by: Timur Tabi ti...@freescale.com --- drivers/watchdog/booke_wdt.c | 19 +-- 1 files changed, 9 insertions(+), 10 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] I2C: Add support for 64bit system.
On Dec 20, 2010, at 8:59 AM, Ben Dooks wrote: On Mon, Dec 20, 2010 at 03:37:34PM +0800, Xulei wrote: Currently I2C_MPC supports 32bit system only, then this modification makes it support 32bit and 64bit system both. Signed-off-by: Xulei b33...@freescale.com This been build or run tested? Yes, Any issues with me applying this via the powerpc.git tree? --- drivers/i2c/busses/Kconfig |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index 9c6170c..3392f4b 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig @@ -422,7 +422,7 @@ config I2C_IXP2000 config I2C_MPC tristate MPC107/824x/85xx/512x/52xx/83xx/86xx -depends on PPC32 +depends on PPC32 || PPC64 help If you say yes to this option, support will be included for the built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, -- 1.7.0.4 -- To unsubscribe from this list: send the line unsubscribe linux-i2c in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Ben Dooks, b...@fluff.org, http://www.fluff.org/ben/ Large Hadron Colada: A large Pina Colada that makes the universe disappear. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] Fix SPE float to integer conversion failure
On Nov 16, 2010, at 8:28 PM, Shan Hai wrote: Conversion from float to integer should based on both the instruction encoding and the sign of the operand. Signed-off-by: Shan Hai shan@windriver.com --- arch/powerpc/math-emu/math_efp.c | 12 1 files changed, 8 insertions(+), 4 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 1/4] drivers/serial/ucc_uart.c: Add of_node_put to avoid memory leak
On Aug 31, 2010, at 10:48 AM, Julia Lawall wrote:
Add a call to of_node_put in the error handling code following a call to
of_find_compatible_node or of_find_node_by_type.
This patch also substantially reorganizes the error handling code in the
function, to that it is possible first to jump to code that frees qe_port
and then to jump to code that also puts np.
The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
// smpl
@r exists@
local idexpression x;
expression E,E1,E2;
statement S;
@@
*x =
(of_find_node_by_path
|of_find_node_by_name
|of_find_node_by_phandle
|of_get_parent
|of_get_next_parent
|of_get_next_child
|of_find_compatible_node
|of_match_node
|of_find_node_by_type
|of_find_node_with_property
|of_find_matching_node
|of_parse_phandle
)(...);
...
if (x == NULL) S
... when != x = E
*if (...) {
... when != of_node_put(x)
when != if (...) { ... of_node_put(x); ... }
(
return +...x...+;
|
* return ...;
)
}
...
(
E2 = x;
|
of_node_put(x);
)
// /smpl
Signed-off-by: Julia Lawall ju...@diku.dk
---
drivers/serial/ucc_uart.c | 67
--
1 file changed, 35 insertions(+), 32 deletions(-)
applied
- k
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Bug in arch/powerpc/sysdev/fsl_gtm.c
On Feb 16, 2011, at 8:59 AM, Jean-Denis Boyer wrote: Hi. There is a bug in the function gtm_set_ref_timer16. When called, it correctly sets the requested timer, but the other timer that shares the register GTCFR is reset. The parameter 'clear' passed to macro clrsetbits_8 should not be a bitwise complement, since the macro already complements it. Here is a patch that should fix this issue. --- linux-2.6.35.11/arch/powerpc/sysdev/fsl_gtm.c +++ linux/arch/powerpc/sysdev/fsl_gtm.c @@ -203,13 +203,10 @@ spin_lock_irqsave(gtm-lock, flags); /* - * Properly reset timers: stop, reset, set up prescalers, reference + * Properly set timers: stop, set up prescalers, reference * value and clear event register. */ - clrsetbits_8(tmr-gtcfr, ~(GTCFR_STP(num) | GTCFR_RST(num)), - GTCFR_STP(num) | GTCFR_RST(num)); - - setbits8(tmr-gtcfr, GTCFR_STP(num)); + setbits8(tmr-gtcfr, GTCFR_STP(num) | GTCFR_RST(num)); if (tmr-gtpsr) out_be16(tmr-gtpsr, psr); If you'd like this applied please re-send w/proper signed-off-by - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH 1/2] ATA: Add FSL sata v2 controller support
On Jan 19, 2011, at 3:07 AM, Xulei wrote: In FSL sata v2 block, the snoop bit of PRDT Word3 description information is at bit28 instead of bit22. This patch adds FSL sata v2 probe and resolve this difference. Signed-off-by: Lei Xu b33...@freescale.com Signed-off-by: Roy Zang tie-fei.z...@freescale.com Acked-by: Jeff Garzik jgar...@redhat.com --- drivers/ata/sata_fsl.c | 25 ++--- 1 files changed, 18 insertions(+), 7 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] I2C: Add support for 64bit system.
On Tue, Mar 15, 2011 at 10:44 AM, Kumar Gala ga...@kernel.crashing.org wrote: On Dec 20, 2010, at 8:59 AM, Ben Dooks wrote: On Mon, Dec 20, 2010 at 03:37:34PM +0800, Xulei wrote: Currently I2C_MPC supports 32bit system only, then this modification makes it support 32bit and 64bit system both. Signed-off-by: Xulei b33...@freescale.com This been build or run tested? Yes, Any issues with me applying this via the powerpc.git tree? I'm concerned about the fact that we have to have two defines to declare code that is 32-bit and 64-bit clean. Technically speaking, all drivers should work in both environments. It seems silly to have PPC32 || PPC64 for everything. Isn't there a generic PPC config option that covers this? -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] I2C: Add support for 64bit system.
On Mar 15, 2011, at 10:56 AM, Timur Tabi wrote: On Tue, Mar 15, 2011 at 10:44 AM, Kumar Gala ga...@kernel.crashing.org wrote: On Dec 20, 2010, at 8:59 AM, Ben Dooks wrote: On Mon, Dec 20, 2010 at 03:37:34PM +0800, Xulei wrote: Currently I2C_MPC supports 32bit system only, then this modification makes it support 32bit and 64bit system both. Signed-off-by: Xulei b33...@freescale.com This been build or run tested? Yes, Any issues with me applying this via the powerpc.git tree? I'm concerned about the fact that we have to have two defines to declare code that is 32-bit and 64-bit clean. Technically speaking, all drivers should work in both environments. It seems silly to have PPC32 || PPC64 for everything. Isn't there a generic PPC config option that covers this? There is, I'll post a new patch that uses it. - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
[PATCH] i2c-mpc: Add support for 64bit system
Currently i2c-mpc supports 32bit system only, this modification makes it supported on both 32-bit and 64-bit systems. The P5020 is the first 64-bit PPC system with the i2c-mpc controller. Based in patch from Xulei b33...@freescale.com Signed-off-by: Kumar Gala ga...@kernel.crashing.org --- drivers/i2c/busses/Kconfig |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index 113505a..107d5c2 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig @@ -433,7 +433,7 @@ config I2C_IXP2000 config I2C_MPC tristate MPC107/824x/85xx/512x/52xx/83xx/86xx - depends on PPC32 + depends on PPC help If you say yes to this option, support will be included for the built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, -- 1.7.2.3 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH][v2] define binding for fsl mpic interrupt controllers
On Jan 19, 2011, at 4:30 PM, Stuart yoder wrote: From: Stuart Yoder stuart.yo...@freescale.com define the binding for compatible = fsl,mpic, including the definition of 4-cell interrupt specifiers. The 3rd and 4th cells are needed to define additional types of interrupt source outside the normal external and internal interrupts in FSL SoCs. Define error interrupt, IPIs, and PIC timer sources. Signed-off-by: Stuart Yoder stuart.yo...@freescale.com --- -version 2 -fix some typos -move defintion of interrupt number to the interrupt type 0 -defined no-reset property -added some examples Documentation/powerpc/dts-bindings/fsl/mpic.txt | 251 +++ 1 files changed, 209 insertions(+), 42 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
ok, it seems that no one is interested to fix Pegasos1 G3 600MHz support. But if someone is capable (i don't have this skill) here what it happens reading from serial debug console untill it freezes with linux-2.6.36.4 Pegasos Boot Strap (c) 2002 bplan GmbH Running on CPU PVR:00083311 PLL setting : 0001 Enable L1 ICache...Done. Setting ROM Defaults...Done. Configuring SDRAM... 0800 1000 Delaying...Done. RAMSIZE = 1800 0004 Reading W83194 : 00FF Done. Setting Front Side Bus to 100MHz...Done. Releasing IDE reset ...Done. Configuring Legacy Devices Initializing KBD...Done. PLL setting : 0003 1000 Done. BIOS: Stage 2 entered arg(FFFC,,1800) BIOS: MachineInfo at 0E68 BIOS: set MemPool limit to BAT size (old=1800 new=1000) BIOS: 0F6FFFE8 bytes added to mempool LoadFromRFS: starting LoadFromRFS: lib module 00 has abs load adr at 00C0 CopyModule: start CopyModule: load address : 00C0 CopyModule: copy module to ram...done ModuleCopy: expanding... done LoadFromRFS: 0001 modules out of 0001 loaded InitLib: start InitLib: call module as OF allocated g_e=0xFD8 (len=19232) install_root: pkg=0xFD53B90 after init_environ e=0xFD8 running nvramrc... after running nvramrc no/bad nvramrc - performing default startup script Bus addresses: 253@2 I/O addresses: 7936@FE002100 Memory addresses: 127M@8804 1.3G@9800 Prefetchable memory addresses: install_ata_disk_driver: reg=0x1000 init_drive: reset controller 0x1000/0x100E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0 init_drive: error=0x1 status=0x50 status2=0x50 init_drive: identify drive: atapi=0 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1000 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB init_drive: error=0x1 status=0x0 status2=0x0 init_drive: identify drive: atapi=1 atapi_cmd: cmdlen=12 atapi_cmd: inlen=8 len=65534 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1010 init_drive: reset controller 0x1010/0x101E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20 init_drive: error=0x20 status=0x20 status2=0x20 ATA-wait-ready: timeout: status=0x20 init_drive: failed install_ata_disk_driver: reg=0x1010 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30 init_drive: error=0x30 status=0x30 status2=0x30 ATA-wait-ready: timeout: status=0x30 init_drive: failed Bus addresses: 254@2 I/O addresses: 8@FE001038 3072@FE001400 48K@FE004000 Memory addresses: 1792@A100 1.2G@A0001000 Prefetchable memory addresses: 12M@FD40 F_INSTALL_CONSOLE: BEGIN F_INSTALL_CONSOLE: ALIASING SCREEN F_INSTALL_CONSOLE: ALIASING KBD EMULATION INT HANDLER ENTERED WITH: INT NO: 15 EAX=0003 EBX= ECX= EDX= ESP= EBP= ESI= EDI= AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP= SI=5CF9 DI= DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC CS:IP = F4 C558 C000 0244 3000 01B4 AC63 0200 UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION F_INSTALL_CONSOLE: END auto-booting... do_load: dev= dlen=0 args= alen=0 do_load: alstr= do_load: path doesn't start with / do_load: diag-device == eth do_load: no args..use the default do_load: diag-file == diag try_load: dev=eth dlen=3 args=diag alen=4 entering main read/eval loop... [...] atapi_cmd: cmdlen=12 atapi_cmd: inlen=2048 len=2048 iso_walk: read: name=zImage.chrp extent=0x44FD size=0x337272 ret=no error iso9660: return R_END file_system: return end (-4089) disk-label return len=3371634 ret=end (-4089) ata_disk_close disk-label close: checking exec type Fcode fcode_is_exec: load=0x40 loadlen=3371634 checking exec type Forth checking exec type ELF f_go: checking exec type Fcode fcode_is_exec: load=0x40 loadlen=3371634 checking exec type Forth checking exec type ELF alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914 alloc_constrained: min 0x0, max 0x, align 0x1000, mask 0x, size 0x332000, addr 0x30 alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1 0xFD54910 u2 0xFD54914 u3 0xFD54918 alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x30 size 0xFD0 alloc_constrained: fsblock 0x0 alloc_constrained: addr[] 0x30 alloc_constrained: bsize[] 0xFD0 alloc_constrained: passed min check
Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden
On Tue, Mar 15, 2011 at 03:52:38PM +0800, Américo Wang wrote: On Tue, Mar 15, 2011 at 2:13 AM, Mahesh J Salgaonkar mah...@linux.vnet.ibm.com wrote: During free we do free all of them including RMO region. But since the rtas region is always on top of RMO, crashkernel memory overlaps rtas region and we endup freeing that even, which is causing the crash. Okay, but with this patch applied, we will just ignore rtas region, right? Correct. Thus, when I echo 0 to free all the 128M crashkernel memory, the final result will be 32M left, which means crash_size will still show 32M. This looks odd. How about skipping the 32M as a whole? I mean once the region being freed has overlap with this rtas region, skip the whole rtas region, and let crash_size show 0? The existing code from crash_shrink_memory() function reduces the crash size to 0 when echo'ed 0. I did test this patchset and verified that /sys/kernel/kexec_crash_size show 0 value. Thanks, -Mahesh. ___ kexec mailing list ke...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec -- Signed-off-by: Mahesh Salgaonkar mah...@linux.vnet.ibm.com ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
On Tue, Mar 15, 2011 at 05:44:49PM +0100, nello martuscielli wrote: But if someone is capable (i don't have this skill) here what it happens reading from serial debug console untill it freezes with linux-2.6.36.4 What is the last kernel version working on that machine? If you have a working kernel and can build kernels, you could try bisecting to identify the change that led to that. Perhaps then someone could have some ideas. With kind regards, -- Baurzhan Ismagulov http://www.kz-easy.com/ ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
Original-Nachricht Datum: Tue, 15 Mar 2011 17:44:49 +0100 Von: nello martuscielli ppc.ad...@gmail.com An: CC: linuxppc-dev@lists.ozlabs.org, acrux @ cruxppc acrux...@libero.it Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ? ok, it seems that no one is interested to fix Pegasos1 G3 600MHz support. But if someone is capable (i don't have this skill) here what it happens reading from serial debug console untill it freezes with linux-2.6.36.4 Pegasos Boot Strap (c) 2002 bplan GmbH Running on CPU PVR:00083311 PLL setting : 0001 Enable L1 ICache... Done. Setting ROM Defaults... Done. Configuring SDRAM... 0800 1000 Delaying...Done. RAMSIZE = 1800 0004 Reading W83194 : 00FF Done. Setting Front Side Bus to 100MHz... Done. Releasing IDE reset ... Done. Configuring Legacy Devices Initializing KBD... Done. PLL setting : 0003 1000 Done. BIOS: Stage 2 entered arg(FFFC,,1800) BIOS: MachineInfo at 0E68 BIOS: set MemPool limit to BAT size (old=1800 new=1000) BIOS: 0F6FFFE8 bytes added to mempool LoadFromRFS: starting LoadFromRFS: lib module 00 has abs load adr at 00C0 CopyModule: start CopyModule: load address : 00C0 CopyModule: copy module to ram...done ModuleCopy: expanding... done LoadFromRFS: 0001 modules out of 0001 loaded InitLib: start InitLib: call module as OF allocated g_e=0xFD8 (len=19232) install_root: pkg=0xFD53B90 after init_environ e=0xFD8 running nvramrc... after running nvramrc no/bad nvramrc - performing default startup script Bus addresses: 253@2 I/O addresses: 7936@FE002100 Memory addresses: 127M@8804 1.3G@9800 Prefetchable memory addresses: install_ata_disk_driver: reg=0x1000 init_drive: reset controller 0x1000/0x100E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0 init_drive: error=0x1 status=0x50 status2=0x50 init_drive: identify drive: atapi=0 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1000 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB init_drive: error=0x1 status=0x0 status2=0x0 init_drive: identify drive: atapi=1 atapi_cmd: cmdlen=12 atapi_cmd: inlen=8 len=65534 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1010 init_drive: reset controller 0x1010/0x101E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20 init_drive: error=0x20 status=0x20 status2=0x20 ATA-wait-ready: timeout: status=0x20 init_drive: failed install_ata_disk_driver: reg=0x1010 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30 init_drive: error=0x30 status=0x30 status2=0x30 ATA-wait-ready: timeout: status=0x30 init_drive: failed Bus addresses: 254@2 I/O addresses: 8@FE001038 3072@FE001400 48K@FE004000 Memory addresses: 1792@A100 1.2G@A0001000 Prefetchable memory addresses: 12M@FD40 F_INSTALL_CONSOLE: BEGIN F_INSTALL_CONSOLE: ALIASING SCREEN F_INSTALL_CONSOLE: ALIASING KBD EMULATION INT HANDLER ENTERED WITH: INT NO: 15 EAX=0003 EBX= ECX= EDX= ESP= EBP= ESI= EDI= AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP= SI=5CF9 DI= DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC CS:IP = F4 C558 C000 0244 3000 01B4 AC63 0200 UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION F_INSTALL_CONSOLE: END auto-booting... do_load: dev= dlen=0 args= alen=0 do_load: alstr= do_load: path doesn't start with / do_load: diag-device == eth do_load: no args..use the default do_load: diag-file == diag try_load: dev=eth dlen=3 args=diag alen=4 entering main read/eval loop... [...] atapi_cmd: cmdlen=12 atapi_cmd: inlen=2048 len=2048 iso_walk: read: name=zImage.chrp extent=0x44FD size=0x337272 ret=no error iso9660: return R_END file_system: return end (-4089) disk-label return len=3371634 ret=end (-4089) ata_disk_close disk-label close: checking exec type Fcode fcode_is_exec: load=0x40 loadlen=3371634 checking exec type Forth checking exec type ELF f_go: checking exec type Fcode fcode_is_exec: load=0x40 loadlen=3371634 checking exec type Forth checking exec type ELF alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914 alloc_constrained: min
Re: [PATCH] powerpc/fsl_msi: Handle msi-available-ranges better
On Jan 17, 2011, at 2:25 PM, Scott Wood wrote: Now handles multiple ranges, doesn't make assumptions about interrupt specifier format, and doesn't claim interrupts that don't correspond to an available range. Also has some better error checking. The device tree binding is updated to clarify some existing assumptions. Signed-off-by: Scott Wood scottw...@freescale.com --- Documentation/powerpc/dts-bindings/fsl/msi-pic.txt |9 ++- arch/powerpc/sysdev/fsl_msi.c | 92 2 files changed, 64 insertions(+), 37 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
Hi Kumar, I allready had it in the watchdog tree for a couple of weeks (and thus also in linux-next). Are you going to sent it of to Linus or will I sent it over via the watchdog tree? Thanks in advance, Wim. On Feb 8, 2011, at 5:39 PM, Timur Tabi wrote: Improve the status messages that are displayed during some operations of the PowerPC watchdog timer driver. When the watchdog is enabled, the timeout is displayed as a number of seconds, instead of an obscure period. The period is the position of a bit in a 64-bit timer register. The higher the value, the quicker the watchdog timeout occurs. Some people chose a high period value for the timer and get confused as to why the board resets within a few seconds. Messages displayed during open and close are now debug messages, so that they don't clutter the console by default. Finally, printk() is replaced with the pr_xxx() equivalent. Signed-off-by: Timur Tabi ti...@freescale.com --- drivers/watchdog/booke_wdt.c | 19 +-- 1 files changed, 9 insertions(+), 10 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] i2c-mpc: Add support for 64bit system
On Tue, Mar 15, 2011 at 11:02:43AM -0500, Kumar Gala wrote: Currently i2c-mpc supports 32bit system only, this modification makes it supported on both 32-bit and 64-bit systems. The P5020 is the first 64-bit PPC system with the i2c-mpc controller. Based in patch from Xulei b33...@freescale.com Signed-off-by: Kumar Gala ga...@kernel.crashing.org ok, will add to -next --- drivers/i2c/busses/Kconfig |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig index 113505a..107d5c2 100644 --- a/drivers/i2c/busses/Kconfig +++ b/drivers/i2c/busses/Kconfig @@ -433,7 +433,7 @@ config I2C_IXP2000 config I2C_MPC tristate MPC107/824x/85xx/512x/52xx/83xx/86xx - depends on PPC32 + depends on PPC help If you say yes to this option, support will be included for the built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, -- 1.7.2.3 -- Ben Dooks, b...@fluff.org, http://www.fluff.org/ben/ Large Hadron Colada: A large Pina Colada that makes the universe disappear. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
On Tue, Mar 15, 2011 at 06:14:48PM +0100, Gerhard Pircher wrote: Original-Nachricht Datum: Tue, 15 Mar 2011 17:44:49 +0100 Von: nello martuscielli ppc.ad...@gmail.com An: CC: linuxppc-dev@lists.ozlabs.org, acrux @ cruxppc acrux...@libero.it Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ? ok, it seems that no one is interested to fix Pegasos1 G3 600MHz support. But if someone is capable (i don't have this skill) here what it happens reading from serial debug console untill it freezes with linux-2.6.36.4 Pegasos Boot Strap (c) 2002 bplan GmbH Running on CPU PVR:00083311 PLL setting : 0001 Enable L1 ICache... Done. Setting ROM Defaults... Done. Configuring SDRAM... 0800 1000 Delaying...Done. RAMSIZE = 1800 0004 Reading W83194 : 00FF Done. Setting Front Side Bus to 100MHz... Done. Releasing IDE reset ... Done. Configuring Legacy Devices Initializing KBD... Done. PLL setting : 0003 1000 Done. BIOS: Stage 2 entered arg(FFFC,,1800) BIOS: MachineInfo at 0E68 BIOS: set MemPool limit to BAT size (old=1800 new=1000) BIOS: 0F6FFFE8 bytes added to mempool LoadFromRFS: starting LoadFromRFS: lib module 00 has abs load adr at 00C0 CopyModule: start CopyModule: load address : 00C0 CopyModule: copy module to ram...done ModuleCopy: expanding... done LoadFromRFS: 0001 modules out of 0001 loaded InitLib: start InitLib: call module as OF allocated g_e=0xFD8 (len=19232) install_root: pkg=0xFD53B90 after init_environ e=0xFD8 running nvramrc... after running nvramrc no/bad nvramrc - performing default startup script Bus addresses: 253@2 I/O addresses: 7936@FE002100 Memory addresses: 127M@8804 1.3G@9800 Prefetchable memory addresses: install_ata_disk_driver: reg=0x1000 init_drive: reset controller 0x1000/0x100E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0 init_drive: error=0x1 status=0x50 status2=0x50 init_drive: identify drive: atapi=0 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1000 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB init_drive: error=0x1 status=0x0 status2=0x0 init_drive: identify drive: atapi=1 atapi_cmd: cmdlen=12 atapi_cmd: inlen=8 len=65534 install_ata_disk_driver: return no error (0) install_ata_disk_driver: reg=0x1010 init_drive: reset controller 0x1010/0x101E init_drive: allow 4-bits for heads init_drive: select drive 0 init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20 init_drive: error=0x20 status=0x20 status2=0x20 ATA-wait-ready: timeout: status=0x20 init_drive: failed install_ata_disk_driver: reg=0x1010 init_drive: allow 4-bits for heads init_drive: select drive 1 init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30 init_drive: error=0x30 status=0x30 status2=0x30 ATA-wait-ready: timeout: status=0x30 init_drive: failed Bus addresses: 254@2 I/O addresses: 8@FE001038 3072@FE001400 48K@FE004000 Memory addresses: 1792@A100 1.2G@A0001000 Prefetchable memory addresses: 12M@FD40 F_INSTALL_CONSOLE: BEGIN F_INSTALL_CONSOLE: ALIASING SCREEN F_INSTALL_CONSOLE: ALIASING KBD EMULATION INT HANDLER ENTERED WITH: INT NO: 15 EAX=0003 EBX= ECX= EDX= ESP= EBP= ESI= EDI= AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP= SI=5CF9 DI= DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC CS:IP = F4 C558 C000 0244 3000 01B4 AC63 0200 UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION F_INSTALL_CONSOLE: END auto-booting... do_load: dev= dlen=0 args= alen=0 do_load: alstr= do_load: path doesn't start with / do_load: diag-device == eth do_load: no args..use the default do_load: diag-file == diag try_load: dev=eth dlen=3 args=diag alen=4 entering main read/eval loop... [...] atapi_cmd: cmdlen=12 atapi_cmd: inlen=2048 len=2048 iso_walk: read: name=zImage.chrp extent=0x44FD size=0x337272 ret=no error iso9660: return R_END file_system: return end (-4089) disk-label return len=3371634 ret=end (-4089) ata_disk_close disk-label close: checking exec type Fcode fcode_is_exec: load=0x40 loadlen=3371634 checking exec type Forth checking exec type ELF f_go: checking
Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
On Mar 15, 2011, at 1:19 PM, Wim Van Sebroeck wrote: Hi Kumar, I allready had it in the watchdog tree for a couple of weeks (and thus also in linux-next). Are you going to sent it of to Linus or will I sent it over via the watchdog tree? Thanks in advance, Wim. I'll drop it from my tree. - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
[PATCH] update name of pic-no-reset property
From: Stuart Yoder stuart.yo...@freescale.com -changed name from 'no-reset' to 'pic-not-reset' be consisent with Meador Inge's open pic binding patch -update definition Signed-off-by: Stuart Yoder stuart.yo...@freescale.com --- Documentation/powerpc/dts-bindings/fsl/mpic.txt |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/powerpc/dts-bindings/fsl/mpic.txt b/Documentation/powerpc/dts-bindings/fsl/mpic.txt index fdf97c5..8b76e0f 100644 --- a/Documentation/powerpc/dts-bindings/fsl/mpic.txt +++ b/Documentation/powerpc/dts-bindings/fsl/mpic.txt @@ -44,7 +44,7 @@ PROPERTIES Value type: u32 Definition: Shall be 0. - - no-reset + - pic-no-reset Usage: optional Value type: empty Definition: The presence of this property specifies that the @@ -53,7 +53,10 @@ PROPERTIES configuration registers to a sane state-- masked or directed at other cores. This ensures that the client program will not receive interrupts for sources not belonging - to the client. + to the client. The presence of this property also mandates + that any initialization related to interrupt sources shall + be limited to sources explicitly referenced in the device tree. + INTERRUPT SPECIFIER DEFINITION -- 1.7.2.2 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] update name of pic-no-reset property
On Mar 15, 2011, at 1:37 PM, Stuart Yoder wrote: From: Stuart Yoder stuart.yo...@freescale.com -changed name from 'no-reset' to 'pic-not-reset' be consisent with Meador Inge's open pic binding patch -update definition Signed-off-by: Stuart Yoder stuart.yo...@freescale.com --- Documentation/powerpc/dts-bindings/fsl/mpic.txt |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) applied, I squashed this with the mpic binding patch. - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] powerpc: sysdev: fix signedness bug
On Oct 17, 2010, at 9:51 AM, Vasiliy Kulikov wrote: sram_params.sram_size and sram_params.sram_offset were unsigned. If get_cache_sram_size() or get_cache_sram_offset() returns error code then it is not seen to the caller. Made sram_size and sram_offset signed. Signed-off-by: Vasiliy Kulikov sego...@gmail.com --- arch/powerpc/sysdev/fsl_85xx_l2ctlr.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) applied - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] powerpc/fsl-booke: Add e500mc smp defconfig
On Oct 14, 2010, at 8:51 AM, Timur Tabi wrote: On Thu, Oct 14, 2010 at 8:25 AM, Kumar Gala ga...@kernel.crashing.org wrote: +CONFIG_MATH_EMULATION=y Don't these chips have hardware FP? removed. +CONFIG_E1000=y +CONFIG_E1000E=y Are you sure you want these on by default? We may use the E1000 cards in-house, but I don't know if our customers do. leaving, customers can always disable +CONFIG_MSDOS_FS=m +CONFIG_VFAT_FS=y +CONFIG_NTFS_FS=y leaving since we deal with USB flashes and MMC cards which could be MSDOS, VFAT, etc. - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
Original-Nachricht
Datum: Tue, 15 Mar 2011 18:49:24 +0100
Von: Sven Luther s...@z-innov.com
An: Gerhard Pircher gerhard_pirc...@gmx.net
CC: nello martuscielli ppc.ad...@gmail.com, linuxppc-dev@lists.ozlabs.org,
acrux...@libero.it
Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
On Tue, Mar 15, 2011 at 06:14:48PM +0100, Gerhard Pircher wrote:
[...]
On the other side you mentioned this workaround in
arch/ppc/kernel/prom_init.c to me some time ago:
unsigned long __init prom_init(int r3, int r4, prom_entry pp) :
node = call_prom(finddevice, 1, 1, /);
rc = call_prom(getprop, 4, 1, node, model, model,
sizeof(model));
if (rc 0 !strncmp (model, Pegasos, 7)
strncmp (model, Pegasos2, 8)) {
/* Pegasos 1 has a broken translate method in the OF,
* and furthermore the BATs are mapped 1:1 so the phys
* address calculated above is correct, so let's use
* it directly.
*/
} else if (offset == 0) {
/* If we are already running at 0xc000, we assume
we were
* loaded by an OF bootloader which did set a BAT for
us.
* This breaks OF translate so we force phys to be 0.
*/
prom_print((already at 0xc000) phys=0\n);
phys = 0;
} else if (call_prom(getprop, 4, 1, prom_chosen, mmu,
prom_mmu, sizeof(prom_mmu)) = 0) {
prom_print( no MMU found\n);
} else if (call_prom_ret(call-method, 4, 4, result,
translate,
prom_mmu, _stext, 1) != 0) {
prom_print( (translate failed)\n);
} else {
/* We assume the phys. address size is 3 cells */
phys = result[2];
}
Can anybody comment, if this broken translate method in the OF would
still be needed for arch/powerpc?
Well, since this is long dead hardware not produced anymore, i don't see
how the OF could have unbroken itself by moving to powerpc.
It has been age since i looked into this, but to the best of my knowledge
(and i wrote the above code or at least the earlier versions) it should
be still broken.
Any idea then, how the workaround can be ported to arch/powerpc/ or if
there is a better one available?
regards,
Gerhard
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
[git pull] Please pull powerpc.git next branch
The following changes since commit 964a29962c278ddff8a199f23d7c9ef35152a0fe:
powerpc/pseries: Disable MSI using new interface if possible (2011-03-11
14:18:24 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git next
Anatolij Gustschin (1):
powerpc/mpc8xxx_gpio: simplify searching for 'fsl, qoriq-gpio' compatiable
Holger Brunck (3):
powerpc/83xx: rename and update kmeter1
powerpc/82xx: rename and update mgcoge board support
powerpc/8xx: remove obsolete mgsuvd board
Julia Lawall (1):
drivers/serial/ucc_uart.c: Add of_node_put to avoid memory leak
Kumar Gala (1):
powerpc/85xx: Fix writing to spin table 'cpu-release-addr' on ppc64e
Liu Yu (1):
powerpc/85xx: Workaroudn e500 CPU erratum A005
Prabhakar Kushwaha (1):
powerpc/fsl_pci: Add support for FSL PCIe controllers v2.x
Scott Wood (1):
powerpc/fsl_msi: Handle msi-available-ranges better
Shan Hai (1):
powerpc/85xx: Fix SPE float to integer conversion failure
Stuart Yoder (1):
powerpc/fsl: define binding for fsl mpic interrupt controllers
Vasiliy Kulikov (1):
powerpc/85xx: Fix signedness bug in cache-sram
Vivek Mahajan (1):
powerpc/fsl: 85xx: document cache sram bindings
Xulei (2):
ATA: Add FSL sata v2 controller support
powerpc/85xx: Update sata controller compatible for p1022ds board
.../devicetree/bindings/powerpc/fsl/cache_sram.txt | 20 ++
.../devicetree/bindings/powerpc/fsl/mpic.txt | 253
.../devicetree/bindings/powerpc/fsl/msi-pic.txt|9 +-
arch/powerpc/boot/dts/kmeter1.dts | 69 +++---
arch/powerpc/boot/dts/mgcoge.dts | 47 ++--
arch/powerpc/boot/dts/mgsuvd.dts | 163 -
arch/powerpc/boot/dts/p1022ds.dts |4 +-
arch/powerpc/configs/83xx/kmeter1_defconfig|7 +-
arch/powerpc/configs/mgcoge_defconfig |9 +-
arch/powerpc/configs/mgsuvd_defconfig | 81 ---
arch/powerpc/include/asm/reg.h |2 +
arch/powerpc/math-emu/math_efp.c | 65 +-
arch/powerpc/platforms/82xx/Makefile |2 +-
arch/powerpc/platforms/82xx/{mgcoge.c = km82xx.c} | 62 --
arch/powerpc/platforms/83xx/Makefile |2 +-
.../powerpc/platforms/83xx/{kmeter1.c = km83xx.c} | 46 +++--
arch/powerpc/platforms/85xx/smp.c |6 +-
arch/powerpc/platforms/8xx/Kconfig |6 -
arch/powerpc/platforms/8xx/Makefile|1 -
arch/powerpc/platforms/8xx/mgsuvd.c| 92 ---
arch/powerpc/sysdev/fsl_85xx_l2ctlr.c |4 +-
arch/powerpc/sysdev/fsl_msi.c | 92 +---
arch/powerpc/sysdev/fsl_pci.c | 15 +-
arch/powerpc/sysdev/fsl_pci.h | 17 +-
arch/powerpc/sysdev/mpc8xxx_gpio.c |4 +-
drivers/ata/sata_fsl.c | 25 ++-
drivers/tty/serial/ucc_uart.c | 67 +++---
27 files changed, 584 insertions(+), 586 deletions(-)
create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/cache_sram.txt
delete mode 100644 arch/powerpc/boot/dts/mgsuvd.dts
delete mode 100644 arch/powerpc/configs/mgsuvd_defconfig
rename arch/powerpc/platforms/82xx/{mgcoge.c = km82xx.c} (69%)
rename arch/powerpc/platforms/83xx/{kmeter1.c = km83xx.c} (80%)
delete mode 100644 arch/powerpc/platforms/8xx/mgsuvd.c
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
[PATCH] crypto: caam - de-CHIP-ify device tree compatibles
- all the integration parameters have been captured by the binding.
- the block name really uniquely identifies this hardware.
Some advocate putting SoC names everywhere in case software needs
to work around some chip-specific bug, but more precise SoC
information already exists in SVR, and board information already
exists in the top-level device tree node.
Note that sometimes the SoC name is a worse identifier than the
block version, as the block version can change between revisions
of the same SoC.
As a matter of historical reference, neither SEC versions 2.x
nor 3.x (driven by talitos) ever needed CHIP references.
Signed-off-by: Kim Phillips kim.phill...@freescale.com
Cc: Kumar Gala kumar.g...@freescale.com
Cc: Scott Wood scottw...@freescale.com
---
.../devicetree/bindings/crypto/fsl-sec4.txt| 64
arch/powerpc/boot/dts/p4080ds.dts | 32 ---
2 files changed, 37 insertions(+), 59 deletions(-)
diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
index 568aa3c..bf57ecd 100644
--- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
+++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
@@ -38,7 +38,7 @@ in the memory partition devoted to a particular core. The
P4080 has 4 JRs, so
up to 4 JRs can be configured; and all 4 JRs process requests in parallel.
=
-P4080 SEC 4 Node
+SEC 4 Node
Description
@@ -53,7 +53,7 @@ PROPERTIES
- compatible
Usage: required
Value type: string
- Definition: Must include fsl,p4080-sec-v4.0,fsl,sec-v4.0
+ Definition: Must include fsl,sec-v4.0
- #address-cells
Usage: required
@@ -105,7 +105,7 @@ PROPERTIES
EXAMPLE
crypto@30 {
- compatible = fsl,p4080-sec-v4.0, fsl,sec-v4.0;
+ compatible = fsl,sec-v4.0;
#address-cells = 1;
#size-cells = 1;
reg = 0x30 0x1;
@@ -115,7 +115,7 @@ EXAMPLE
};
=
-P4080 Job Ring (JR) Node
+Job Ring (JR) Node
Child of the crypto node defines data processing interface to SEC 4
across the peripheral bus for purposes of processing
@@ -127,7 +127,7 @@ P4080 Job Ring (JR) Node
- compatible
Usage: required
Value type: string
- Definition: Must include
fsl,p4080-sec-v4.0-job-ring,fsl,sec-v4.0-job-ring
+ Definition: Must include fsl,sec-v4.0-job-ring
- reg
Usage: required
@@ -163,8 +163,7 @@ P4080 Job Ring (JR) Node
EXAMPLE
jr@1000 {
- compatible = fsl,p4080-sec-v4.0-job-ring,
-fsl,sec-v4.0-job-ring;
+ compatible = fsl,sec-v4.0-job-ring;
reg = 0x1000 0x1000;
fsl,liodn = 0x081;
interrupt-parent = mpic;
@@ -173,7 +172,7 @@ EXAMPLE
=
-P4080 Run Time Integrity Check (RTIC) Node
+Run Time Integrity Check (RTIC) Node
Child node of the crypto node. Defines a register space that
contains up to 5 sets of addresses and their lengths (sizes) that
@@ -186,7 +185,7 @@ P4080 Run Time Integrity Check (RTIC) Node
- compatible
Usage: required
Value type: string
- Definition: Must include fsl,p4080-sec-v4.0-rtic,fsl,sec-v4.0-rtic.
+ Definition: Must include fsl,sec-v4.0-rtic.
- #address-cells
Usage: required
@@ -219,8 +218,7 @@ P4080 Run Time Integrity Check (RTIC) Node
EXAMPLE
rtic@6000 {
- compatible = fsl,p4080-sec-v4.0-rtic,
-fsl,sec-v4.0-rtic;
+ compatible = fsl,sec-v4.0-rtic;
#address-cells = 1;
#size-cells = 1;
reg = 0x6000 0x100;
@@ -228,7 +226,7 @@ EXAMPLE
};
=
-P4080 Run Time Integrity Check (RTIC) Memory Node
+Run Time Integrity Check (RTIC) Memory Node
A child node that defines individual RTIC memory regions that are used to
perform run-time integrity check of memory areas that should not modified.
The node defines a register that contains the memory address
@@ -238,7 +236,7 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
- compatible
Usage: required
Value type: string
- Definition: Must include
fsl,p4080-sec-v4.0-rtic-memory,fsl,sec-v4.0-rtic-memory.
+ Definition: Must include fsl,sec-v4.0-rtic-memory.
- reg
Usage: required
@@ -270,15 +268,14 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
EXAMPLE
rtic-a@0 {
- compatible = fsl,p4080-sec-v4.0-rtic-memory,
-fsl,sec-v4.0-rtic-memory;
+ compatible = fsl,sec-v4.0-rtic-memory;
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote: Well, since this is long dead hardware not produced anymore, i don't see how the OF could have unbroken itself by moving to powerpc. It has been age since i looked into this, but to the best of my knowledge (and i wrote the above code or at least the earlier versions) it should be still broken. Any idea then, how the workaround can be ported to arch/powerpc/ or if there is a better one available? Sorry, it has been years since i looked these parts of the linux kernel, so i don't really know how the arch/powerpc code handles this differently. Your best guess is to hunt for the code yourself, and find the place. I don't remember though if debugging at that time is easily possible though. Friendly, Sven Luther ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 15 Mar 2011 22:41:49 +0100 Sven Luther sven.lut...@z-innov.com wrote: On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote: Well, since this is long dead hardware not produced anymore, i don't see how the OF could have unbroken itself by moving to powerpc. It has been age since i looked into this, but to the best of my knowledge (and i wrote the above code or at least the earlier versions) it should be still broken. Any idea then, how the workaround can be ported to arch/powerpc/ or if there is a better one available? Sorry, it has been years since i looked these parts of the linux kernel, so i don't really know how the arch/powerpc code handles this differently. Your best guess is to hunt for the code yourself, and find the place. I don't remember though if debugging at that time is easily possible though. if chrp support doesn't anymore include Pegasos1 it could be nice to remove all that dead code. Albeit it's fun that nobody cared about for it during the ppc=powerpc switch as Pegasos1 was retired in 2003 and linux-2.6.17 was released in 2006... about three years. my regards, Nico - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk2AAvwACgkQxq34tDeO7LiAMgCfSOueU5IE+CGJQFm56C2vIQdl WpUAn1MsjAZb/nt1SFtfiB1gLdx79lwX =LULL -END PGP SIGNATURE- ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
On Tue, Mar 15, 2011 at 04:52:20PM -0500, Kim Phillips wrote:
- all the integration parameters have been captured by the binding.
- the block name really uniquely identifies this hardware.
Some advocate putting SoC names everywhere in case software needs
to work around some chip-specific bug, but more precise SoC
information already exists in SVR, and board information already
exists in the top-level device tree node.
Note that sometimes the SoC name is a worse identifier than the
block version, as the block version can change between revisions
of the same SoC.
As a matter of historical reference, neither SEC versions 2.x
nor 3.x (driven by talitos) ever needed CHIP references.
Signed-off-by: Kim Phillips kim.phill...@freescale.com
sigh Very well. As long as some level of versioning is used on the
compatible values, I guess I can live with it.
Acked-off-by: Grant Likely grant.lik...@secretlab.ca
Cc: Kumar Gala kumar.g...@freescale.com
Cc: Scott Wood scottw...@freescale.com
---
.../devicetree/bindings/crypto/fsl-sec4.txt| 64
arch/powerpc/boot/dts/p4080ds.dts | 32 ---
2 files changed, 37 insertions(+), 59 deletions(-)
diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
index 568aa3c..bf57ecd 100644
--- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
+++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
@@ -38,7 +38,7 @@ in the memory partition devoted to a particular core. The
P4080 has 4 JRs, so
up to 4 JRs can be configured; and all 4 JRs process requests in parallel.
=
-P4080 SEC 4 Node
+SEC 4 Node
Description
@@ -53,7 +53,7 @@ PROPERTIES
- compatible
Usage: required
Value type: string
- Definition: Must include fsl,p4080-sec-v4.0,fsl,sec-v4.0
+ Definition: Must include fsl,sec-v4.0
- #address-cells
Usage: required
@@ -105,7 +105,7 @@ PROPERTIES
EXAMPLE
crypto@30 {
- compatible = fsl,p4080-sec-v4.0, fsl,sec-v4.0;
+ compatible = fsl,sec-v4.0;
#address-cells = 1;
#size-cells = 1;
reg = 0x30 0x1;
@@ -115,7 +115,7 @@ EXAMPLE
};
=
-P4080 Job Ring (JR) Node
+Job Ring (JR) Node
Child of the crypto node defines data processing interface to SEC 4
across the peripheral bus for purposes of processing
@@ -127,7 +127,7 @@ P4080 Job Ring (JR) Node
- compatible
Usage: required
Value type: string
- Definition: Must include
fsl,p4080-sec-v4.0-job-ring,fsl,sec-v4.0-job-ring
+ Definition: Must include fsl,sec-v4.0-job-ring
- reg
Usage: required
@@ -163,8 +163,7 @@ P4080 Job Ring (JR) Node
EXAMPLE
jr@1000 {
- compatible = fsl,p4080-sec-v4.0-job-ring,
- fsl,sec-v4.0-job-ring;
+ compatible = fsl,sec-v4.0-job-ring;
reg = 0x1000 0x1000;
fsl,liodn = 0x081;
interrupt-parent = mpic;
@@ -173,7 +172,7 @@ EXAMPLE
=
-P4080 Run Time Integrity Check (RTIC) Node
+Run Time Integrity Check (RTIC) Node
Child node of the crypto node. Defines a register space that
contains up to 5 sets of addresses and their lengths (sizes) that
@@ -186,7 +185,7 @@ P4080 Run Time Integrity Check (RTIC) Node
- compatible
Usage: required
Value type: string
- Definition: Must include fsl,p4080-sec-v4.0-rtic,fsl,sec-v4.0-rtic.
+ Definition: Must include fsl,sec-v4.0-rtic.
- #address-cells
Usage: required
@@ -219,8 +218,7 @@ P4080 Run Time Integrity Check (RTIC) Node
EXAMPLE
rtic@6000 {
- compatible = fsl,p4080-sec-v4.0-rtic,
- fsl,sec-v4.0-rtic;
+ compatible = fsl,sec-v4.0-rtic;
#address-cells = 1;
#size-cells = 1;
reg = 0x6000 0x100;
@@ -228,7 +226,7 @@ EXAMPLE
};
=
-P4080 Run Time Integrity Check (RTIC) Memory Node
+Run Time Integrity Check (RTIC) Memory Node
A child node that defines individual RTIC memory regions that are used to
perform run-time integrity check of memory areas that should not modified.
The node defines a register that contains the memory address
@@ -238,7 +236,7 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
- compatible
Usage: required
Value type: string
- Definition: Must include
fsl,p4080-sec-v4.0-rtic-memory,fsl,sec-v4.0-rtic-memory.
+ Definition: Must include fsl,sec-v4.0-rtic-memory.
