* [PATCH v2] sbc8560: Fix warm reboot with board specific reset function
From: Paul Gortmaker @ 2009-08-14 14:36 UTC (permalink / raw)
To: Linuxppc-dev
In-Reply-To: <1456507C-E9F9-436B-9901-6F127A5FDD1F@kernel.crashing.org>
From: Liang Li <Liang.Li@windriver.com>
The existing fsl_rstcr_restart function is not applicable to the
mpc8560. The Global Utilities Block on this earlier CPU doesn't have
the control/reset register at 0xe00b0. This implements a board
specific reset function that uses the RCR(Reset Control Register) of
the sbc8560's EPLD to do a reset.
Signed-off-by: Liang Li <Liang.Li@windriver.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
v2: update comment, change outb(x, inb(x)&0x7f) --> clrbits(x,0x80)
arch/powerpc/platforms/85xx/sbc8560.c | 39 ++++++++++++++++++++++++++++++++-
1 files changed, 38 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/platforms/85xx/sbc8560.c b/arch/powerpc/platforms/85xx/sbc8560.c
index cc27807..a5ad1c7 100644
--- a/arch/powerpc/platforms/85xx/sbc8560.c
+++ b/arch/powerpc/platforms/85xx/sbc8560.c
@@ -267,6 +267,43 @@ arch_initcall(sbc8560_rtc_init);
#endif /* M48T59 */
+static __u8 __iomem *brstcr;
+
+static int __init sbc8560_bdrstcr_init(void)
+{
+ struct device_node *np;
+ struct resource res;
+
+ np = of_find_compatible_node(NULL, NULL, "wrs,sbc8560-brstcr");
+ if (np == NULL) {
+ printk(KERN_WARNING "sbc8560: No board specific RSTCR in DTB.\n");
+ return -ENODEV;
+ }
+
+ of_address_to_resource(np, 0, &res);
+
+ printk(KERN_INFO "sbc8560: Found BRSTCR at i/o 0x%x\n", res.start);
+
+ brstcr = ioremap(res.start, res.end - res.start);
+ if(!brstcr)
+ printk(KERN_WARNING "sbc8560: ioremap of brstcr failed.\n");
+
+ of_node_put(np);
+
+ return 0;
+}
+
+arch_initcall(sbc8560_bdrstcr_init);
+
+void sbc8560_rstcr_restart(char * cmd)
+{
+ local_irq_disable();
+ if(brstcr)
+ clrbits8(brstcr, 0x80);
+
+ while(1);
+}
+
define_machine(sbc8560) {
.name = "SBC8560",
.probe = sbc8560_probe,
@@ -274,7 +311,7 @@ define_machine(sbc8560) {
.init_IRQ = sbc8560_pic_init,
.show_cpuinfo = sbc8560_show_cpuinfo,
.get_irq = mpic_get_irq,
- .restart = fsl_rstcr_restart,
+ .restart = sbc8560_rstcr_restart,
.calibrate_decr = generic_calibrate_decr,
.progress = udbg_progress,
};
--
1.6.3.3
^ permalink raw reply related
* Configure CPM2 PORTC pin (PC9) for external interrupt?
From: Baojun Wang @ 2009-08-14 14:27 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
hi, list:
I need to configure CPM2 PORTC pin (PC9) for external interrupt, when I
read the MPC8555ERM.pdf and cpm2-pic.c, I find that PC9 interrupt number is
56, and I request the IRQ in this way:
hw_irq = 56;
virq = irq_create_mapping(cpm2_host, hw_irq);
reqeust_irq(virq, ...);
I can request the irq successfully, but the interrupt is never generated
(ISR is not called) to the PC9 pins, even though the hardware said an
interrupt was raised. (the hardware have a register with a special bit)
Should I configure the cpm2 io port first to allow PORTC interrupt? I have
read the cpm2 io port documentation, and I initialize the PC9 as:
PPARC[pc9_bit] = 0; /* for general purpose IO, not dedicated */
PSORC[pc9_bit] = 0; /* no special option */
PDIRC[pc9_bit] = 0; /* for both input/output */
Am I missing some thing? Any suggestion will be greatly appreciated.
Best Regards,
- Wang
[-- Attachment #2: Type: text/html, Size: 995 bytes --]
^ permalink raw reply
* RE: ARM clock API to PowerPC
From: Benjamin Herrenschmidt @ 2009-08-14 12:07 UTC (permalink / raw)
To: Guennadi Liakhovetski
Cc: devicetree-discuss, John Jacques, linuxppc-dev list, Torez Smith,
Russell King
In-Reply-To: <Pine.LNX.4.64.0908141255230.5980@axis700.grange>
On Fri, 2009-08-14 at 13:29 +0200, Guennadi Liakhovetski wrote:
> but since they are quite long, in short, in them a patch has been
> discussed, that allowed to re-use an MMC driver, used on some MFDs, on
> SuperH SoCs. The patch was taking the "easy route" of adding the
> possibility to use the clock API to the tmio_mmc.c driver, while leaving
> it to use static clock configurations with MFD drivers. This approach has
> been rejected and initially it has been suggested to implement a
> platform-independent clock API like what had been proposed by clocklib,
> but since the future of clocklib is unclear, it has then been decided to
> remove the clock (and power) management from the driver proper and move
> them to some callbacks. I.e., there would be more users interested in a
> unified clock API, including other platforms and platform-independent
> drivers like MFD. Currently the reason, why MFD drivers cannot implement
> their own clock devices is that the "struct clk" differs between
> platforms.
But there is no reason for it to differ !
My idea is that struct clock would contain function pointers for the
enable/disable/get_rate/ etc... methods
Thus it's up to clk_get() to provide an object with the right pointers.
Now, on ARM, it's currently done in such a way that it's mostly up to
the platform (though that's less true with clkdev).
But with the help of the device-tree, it becomes trivial to have
somebody register clock providers (ie, objects that can product struct
clk *) and bind them to driver.
I think struct clk is the way to go. The problem is to sort out the
binding between the clock provider and the driver. The DT is an easy and
nice way to do it for archs that have it. But there are other ways.
Cheers,
Ben.
^ permalink raw reply
* Re: [SATA] Does SATA work with kernel > v2.6.25.7?
From: Wolfgang Denk @ 2009-08-14 11:33 UTC (permalink / raw)
To: Olivier Croset; +Cc: linuxppc-dev
In-Reply-To: <AA253FF7C15741BCAE4B5D4B4FFF16B6@Labo5>
Dear "Olivier Croset",
In message <AA253FF7C15741BCAE4B5D4B4FFF16B6@Labo5> you wrote:
>
> While browsing the web, I found the following message with the same kind of
> errors:
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-03/msg08159.html
>
> It is said that "the sata is only supported up to 2.6.25.7". Is it true for
> all PowerPCs or only for 460EX CPU?
This messages is explicitly about (and only about) the AMCC 460EX
Canyonlands board and the Synopsys DesignWare Cores (DWC) SATA driver
used on this processor.
This has nothing to do with your poblems with a SIL controller.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
When all is said and done, more is said than done.
^ permalink raw reply
* Re: [PATCH 0/3] cpu: idle state framework for offline CPUs.
From: Pavel Machek @ 2009-08-14 11:30 UTC (permalink / raw)
To: Dipankar Sarma
Cc: Brown, Len, Darrick J. Wong, Peter Zijlstra, Gautham R Shenoy,
linux-kernel@vger.kernel.org, Rafael J. Wysocki,
Pallipadi, Venkatesh, Li, Shaohua, Ingo Molnar,
linuxppc-dev@lists.ozlabs.org, Len Brown
In-Reply-To: <20090813045931.GB14649@in.ibm.com>
> > > 2. A low-power state where the guest indicates it doesn't need the
> > > CPU (and can be put in low power state) but doesn't want to give up
> > > its allocated cpu share. IOW, no visible configuration changes.
> > >
> > > So, in any case we would probably want more than one states.
> >
> > How are #1 and #2 different when the hypervisor
> > gets control in all idle states? I assert that
> > they are the same, and thus 1 state will suffice.
>
> It depends on the hypervisor implementation. On pseries (powerpc)
> hypervisor, for example, they are different. By offlining a vcpu
> (and in turn shutting a cpu), you will actually create a configuration
> change in the VM that is visible to other systems management tools
> which may not be what the system administrator wanted. Ideally,
> we would like to distinguish between these two states.
>
> Hope that suffices as an example.
So... you have something like "physically pulling out hotplug cpu" on
powerpc.
But maybe it is useful to take already offline cpus (from linux side),
and make that visible to hypervisor, too.
So maybe something like "echo 1 > /sys/devices/system/cpu/cpu1/unplug"
would be more useful for hypervisor case?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
^ permalink raw reply
* RE: ARM clock API to PowerPC
From: Guennadi Liakhovetski @ 2009-08-14 11:29 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: devicetree-discuss, John Jacques, linuxppc-dev list, Torez Smith,
Russell King
In-Reply-To: <1250242149.24143.36.camel@pasglop>
On Fri, 14 Aug 2009, Benjamin Herrenschmidt wrote:
> On Thu, 2009-08-13 at 16:59 +0800, Li Yang-R58472 wrote:
> > >Now, I know there is at least one person on earth
> > >contemplating sharing some drivers between PPC and ARM. I
> > >won't tell much more at this stage, but it makes sense in the
> > >grand scheme of things to see SoC vendors put similar IO cores
> > >into either PPC or ARM and providing that clock API is a good
> > >way to also allow these drivers to work since the drivers in
> > >questions make use of it.
> >
> > Freescale USB UDC driver is another example that shared between PowerPC
> > and ARM(i.mx). Currently, the imx part of the driver uses clk API, but
> > PowerPC part uses static initialization. It will be better if we can
> > unify the clk setting part of the driver.
>
> I had a look at it looks like it uses the API in a way that would fit
> nicely with my plans, ie, it should be possible to use the same driver
> on both archs pretty much without changes provided the ppc platform
> provides a clock source driver and hooks it up to the device-tree.
>
> I'll work on some proof-of-concept implementation of the core bits
> early next week.
You might have a look at these threads:
http://marc.info/?t=124876760500001&r=1&w=2
http://marc.info/?t=124782904600005&r=2&w=2
but since they are quite long, in short, in them a patch has been
discussed, that allowed to re-use an MMC driver, used on some MFDs, on
SuperH SoCs. The patch was taking the "easy route" of adding the
possibility to use the clock API to the tmio_mmc.c driver, while leaving
it to use static clock configurations with MFD drivers. This approach has
been rejected and initially it has been suggested to implement a
platform-independent clock API like what had been proposed by clocklib,
but since the future of clocklib is unclear, it has then been decided to
remove the clock (and power) management from the driver proper and move
them to some callbacks. I.e., there would be more users interested in a
unified clock API, including other platforms and platform-independent
drivers like MFD. Currently the reason, why MFD drivers cannot implement
their own clock devices is that the "struct clk" differs between
platforms.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
^ permalink raw reply
* [SATA] Does SATA work with kernel > v2.6.25.7?
From: Olivier Croset @ 2009-08-14 10:49 UTC (permalink / raw)
To: linuxppc-dev
Hello everybody,
I'm working on a custom board with a Freescale 8347 CPU and a Silicon Image
SIL3512 SATA controller, which is on the PCI bus.
SATA is working with 2.6.22 but no more with 2.6.30.4. I tried different
parameters in the kernel configuration with no success. I got the following
output when Linux boots:
<snip>
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors: (81.9 GB/76.3 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sda:<6>ata2: SATA link down (SStatus 0 SControl 310)
IP-Config: Complete:
device=eth1, addr=192.0.0.238, mask=255.255.255.0, gw=192.0.0.128,
host=xcom9347, domain=, nis-domain=(none),
bootserver=192.0.0.64, rootserver=192.0.0.64, rootpath=
PHY: mdio@e0024520:09 - Link is Up - 100/Half
ata1: lost interrupt (Status 0x50)
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
ata1: lost interrupt (Status 0x50)
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
unable to read partition table
sd 0:0:0:0: [sda] Attached SCSI disk
<snip>
Then, I can see /dev/sda but not /dev/sda1 (the partition actually exists).
I can get hard drive informations with hdparm -i and -I.
While browsing the web, I found the following message with the same kind of
errors:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-03/msg08159.html
It is said that "the sata is only supported up to 2.6.25.7". Is it true for
all PowerPCs or only for 460EX CPU?
If SATA should work with 2.6.30.4, may I ask you to take a look to my config
file? (http://pastebin.com/f16067607)
Thanks,
Olivier
^ permalink raw reply
* RE: ARM clock API to PowerPC
From: Benjamin Herrenschmidt @ 2009-08-14 9:29 UTC (permalink / raw)
To: Li Yang-R58472
Cc: devicetree-discuss, John Jacques, linuxppc-dev list, Torez Smith,
Russell King
In-Reply-To: <3A45394FD742FA419B760BB8D398F9ED59DE33@zch01exm26.fsl.freescale.net>
On Thu, 2009-08-13 at 16:59 +0800, Li Yang-R58472 wrote:
> >Now, I know there is at least one person on earth
> >contemplating sharing some drivers between PPC and ARM. I
> >won't tell much more at this stage, but it makes sense in the
> >grand scheme of things to see SoC vendors put similar IO cores
> >into either PPC or ARM and providing that clock API is a good
> >way to also allow these drivers to work since the drivers in
> >questions make use of it.
>
> Freescale USB UDC driver is another example that shared between PowerPC
> and ARM(i.mx). Currently, the imx part of the driver uses clk API, but
> PowerPC part uses static initialization. It will be better if we can
> unify the clk setting part of the driver.
I had a look at it looks like it uses the API in a way that would fit
nicely with my plans, ie, it should be possible to use the same driver
on both archs pretty much without changes provided the ppc platform
provides a clock source driver and hooks it up to the device-tree.
I'll work on some proof-of-concept implementation of the core bits
early next week.
Cheers,
Ben.
^ permalink raw reply
* Re: [PATCH] Add kmemleak annotations to lmb.c
From: Catalin Marinas @ 2009-08-14 8:25 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev, David S. Miller
In-Reply-To: <1250236600.24143.34.camel@pasglop>
On Fri, 2009-08-14 at 17:56 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2009-08-13 at 16:40 +0100, Catalin Marinas wrote:
> > On Thu, 2009-08-13 at 13:01 +1000, Michael Ellerman wrote:
> > > We don't actually want kmemleak to track the lmb allocations, so we
> > > pass min_count as 0. However telling kmemleak about lmb allocations
> > > allows it to scan that memory for pointers to other memory that is
> > > tracked by kmemleak, ie. slab allocations etc.
> >
> > Looks alright to me (though I haven't tested it). You can add a
> > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>
> Actually, Milton pointed to me that we may not want to allow all
> LMB chunks to be scanned by kmemleaks, things like the DART hole
> that's taken out of the linear mapping for example may need to
> be avoided, though I'm not sure what would be the right way to
> do it.
I suspect there are more blocks to be scanned than those that shouldn't,
so maybe ignore the latter explicitly using kmemleak_ignore(). This was
raised recently on x86_64 as well which has a memory hole for some
aperture - http://lkml.org/lkml/2009/8/13/237.
--
Catalin
^ permalink raw reply
* Re: [PATCH] Add kmemleak annotations to lmb.c
From: Benjamin Herrenschmidt @ 2009-08-14 7:56 UTC (permalink / raw)
To: Catalin Marinas; +Cc: linuxppc-dev, David S. Miller
In-Reply-To: <1250178041.14019.34.camel@pc1117.cambridge.arm.com>
On Thu, 2009-08-13 at 16:40 +0100, Catalin Marinas wrote:
> On Thu, 2009-08-13 at 13:01 +1000, Michael Ellerman wrote:
> > We don't actually want kmemleak to track the lmb allocations, so we
> > pass min_count as 0. However telling kmemleak about lmb allocations
> > allows it to scan that memory for pointers to other memory that is
> > tracked by kmemleak, ie. slab allocations etc.
>
> Looks alright to me (though I haven't tested it). You can add a
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Actually, Milton pointed to me that we may not want to allow all
LMB chunks to be scanned by kmemleaks, things like the DART hole
that's taken out of the linear mapping for example may need to
be avoided, though I'm not sure what would be the right way to
do it.
Cheers,
Ben.
^ permalink raw reply
* Re: PowerPC kernel linux-2.6.29.6 PANIC's at include/linux/cred.h for ipsec enabled kernel
From: srikanth krishnakar @ 2009-08-14 5:08 UTC (permalink / raw)
To: Linuxppc-dev
In-Reply-To: <6213bc560908102335n2b6a2bc1icb2acafe7f4117@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5141 bytes --]
Hi all,
Target : PowerPC440
Kernel : Linux-2.6.29.6
The issue still remains in kernel linux-2.6.29.6 enabling following options
in kernel, the kernel panics and won't boot anymore
The following kernel options enabled :
# Networking support
CONFIG_NET=y
CONFIG_INET=y
CONFIG_NET_KEY=y
CONFIG_XFRM_USER=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_TUNNEL=y
# IPV6
CONFIG_IPV6=y
CONFIG_IPV6_TUNNEL=y
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
CONFIG_INET6_IPCOMP=y
CONFIG_INET6_TUNNEL=y
# Cryptographic API
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_DEFLATE=y
and while bootup I am seeing the panic/crash message as :
Looking up port of RPC 100005/1 on 10.50.21.151
VFS: Mounted root (nfs filesystem) on device 0:13.
Freeing unused kernel memory: 184k init
INIT: version 2.86 booting
Starting udevudevd version 124 started
Remounting root file system...
------------[ cut here ]------------
kernel BUG at include/linux/cred.h:206!
Oops: Exception in kernel mode, sig: 5 [#1]
PREEMPT LTT NESTING LEVEL : 0
Xilinx PPC440
Modules linked in:
NIP: c00a8414 LR: c0067804 CTR: c00a83ec
REGS: ce977da0 TRAP: 0700 Not tainted (2.6.29.6-ipsec)
MSR: 00029000 <EE,ME,CE> CR: 24028448 XER: 00000005
TASK = cf9a9430[472] 'mount.sh' THREAD: ce976000
GPR00: ffffffff ce977e50 cf9a9430 cf9e00c0 cf3c7ee0 fffeb038 00000003 c04f2224
GPR08: 000000bf 00000001 cf8070e0 c05255e8 44022444 100db7bc 4802e5a4 bf9f09c8
GPR16: c0456670 00000000 c0511188 c05111a8 c0525624 00000001 c0522ca0 ce976034
GPR24: c0511328 ce976034 ce976000 c05255e8 00000003 cf3c7160 c00a83ec cf99aaa0
NIP [c00a8414] file_free_rcu+0x28/0x6c
LR [c0067804] __rcu_process_callbacks+0x1e4/0x400
Call Trace:
[ce977e50] [c00a8444] file_free_rcu+0x58/0x6c (unreliable)
[ce977e60] [c0067804] __rcu_process_callbacks+0x1e4/0x400
[ce977e90] [c0067a4c] rcu_process_callbacks+0x2c/0x4c
[ce977eb0] [c0038cb0] __do_softirq+0xfc/0x1e0
[ce977f00] [c0004124] do_softirq+0x5c/0x60
[ce977f10] [c0038b18] irq_exit+0x98/0xc4
[ce977f20] [c000b2b4] timer_interrupt+0x104/0x1cc
[ce977f40] [c000e7d8] ret_from_except+0x0/0x18
Instruction dump:
4832cfa9 4bffffd8 9421fff0 7c0802a6 93e1000c 7c7f1b78 90010014 8063003c
81230000 3809ffff 7d290378 55290ffe <0f090000> 7c001828 3000ffff 7c00192d
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..
Any suggestions or the filed bug report anywhere ??
-Srikant
On Tue, Aug 11, 2009 at 12:05 PM, srikanth krishnakar <skrishnakar@gmail.com
> wrote:
> Hi All,
>
> Target : PowerPC (ppc440)
>
> While testing kernel linux-2.6.29.6 with IPSEC enabled I observed frequent
> panic messages as shown below while bootup:
>
> VFS: Mounted root (nfs filesystem) on device 0:13.
>
> Freeing unused kernel memory: 184k init
> INIT: version 2.86 booting
> Starting udevudevd version 124 started
>
> Remounting root file system...
> logger: mount: mount point /proc/bus/usb does not exist
> FAT: invalid media value (0x01)
>
> VFS: Can't find a valid FAT filesystem on dev xsa.
> ------------[ cut here ]------------
> kernel BUG at include/linux/cred.h:206!
> Oops: Exception in kernel mode, sig: 5 [#1]
> PREEMPT LTT NESTING LEVEL : 0
>
> Xilinx Virtex440
> Modules linked in: nls_iso8859_1
> NIP: c0031800 LR: c0031864 CTR: c0033e2c
> REGS: c0515d00 TRAP: 0700 Not tainted (2.6.29.6.xilinx-ml507.0908071454-ipsec)
> MSR: 00029000 <EE,ME,CE> CR: 24028028 XER: 00000005
>
> TASK = c04e74c0[0] 'swapper' THREAD: c0514000
> GPR00: ffffffff c0515db0 c04e74c0 cf9e0120 c00539b4 00000002 ffffffff c04f2224
> GPR08: 000002fd 00000001 000002fc c05255e8 44022024 ffffd6c4 dce9ee1f bfefe53f
>
> GPR16: c0456690 00000000 c0511188 c05111a8 c0525624 00000001 c0522ca0 c0514034
> GPR24: c0511328 c0514034 c0514000 c05255e8 0000000a cf3e7920 ce89e050 ce89e050
> NIP [c0031800] __put_task_struct+0x8c/0xf4
> LR [c0031864] __put_task_struct+0xf0/0xf4
>
> Call Trace:
> [c0515db0] [c0031864] __put_task_struct+0xf0/0xf4 (unreliable)
> [c0515dc0] [c0033ecc] delayed_put_task_struct+0xa0/0xbc
> [c0515de0] [c0067804] __rcu_process_callbacks+0x1e4/0x400
> [c0515e10] [c0067a4c] rcu_process_callbacks+0x2c/0x4c
>
> [c0515e30] [c0038cb0] __do_softirq+0xfc/0x1e0
> [c0515e80] [c0004124] do_softirq+0x5c/0x60
> [c0515e90] [c0038b18] irq_exit+0x98/0xc4
> [c0515ea0] [c000b2b4] timer_interrupt+0x104/0x1cc
> [c0515ec0] [c000e7d8] ret_from_except+0x0/0x18
>
> [c0515f80] [c0007294] cpu_idle+0x58/0xf4
> [c0515fa0] [c03db4dc] __got2_end+0x80/0x94
> [c0515fc0] [c04b6734] start_kernel+0x25c/0x2b0
> [c0515ff0] [c0000218] skpinv+0x1a8/0x1e4
> Instruction dump:
> 0f090000 7c001828 3000ffff 7c00192d 40a2fff4 2f800000 419e0078 807f01a4
>
> 81230000 3809ffff 7d290378 55290ffe <0f090000> 7c001828 3000ffff 7c00192d
> Kernel panic - not syncing: Fatal exception in interrupt
> Rebooting in 180 seconds..
>
>
> Attachment: kernel config
>
> your early comments are appreciated !
>
>
>
> Regards
> Srikanth Krishnakar
> **********************
>
--
"The Good You Do, The Best You GET"
Regards
Srikanth Krishnakar
**********************
[-- Attachment #2: Type: text/html, Size: 5905 bytes --]
^ permalink raw reply
* Re: [PATCH] sbc8560: Fix warm reboot with board specific reset function
From: Kumar Gala @ 2009-08-14 4:39 UTC (permalink / raw)
To: Paul Gortmaker; +Cc: linuxppc-dev
In-Reply-To: <1250204775-5001-1-git-send-email-paul.gortmaker@windriver.com>
On Aug 13, 2009, at 6:06 PM, Paul Gortmaker wrote:
> From: Liang Li <Liang.Li@windriver.com>
>
> The existing fsl_rstcr_restart function fails to reset the sbc8560
> board. This implements a board specific reset function that uses
> the RCR(Reset Control Register) of the board's EPLD to do a reset.
>
> Signed-off-by: Liang Li <Liang.Li@windriver.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
> arch/powerpc/platforms/85xx/sbc8560.c | 39 ++++++++++++++++++++++++
> ++++++++-
> 1 files changed, 38 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/platforms/85xx/sbc8560.c b/arch/powerpc/
> platforms/85xx/sbc8560.c
> index cc27807..86dcca2 100644
> --- a/arch/powerpc/platforms/85xx/sbc8560.c
> +++ b/arch/powerpc/platforms/85xx/sbc8560.c
> @@ -267,6 +267,43 @@ arch_initcall(sbc8560_rtc_init);
>
> #endif /* M48T59 */
>
> +static __u8 __iomem *brstcr;
> +
> +static int __init sbc8560_bdrstcr_init(void)
> +{
> + struct device_node *np;
> + struct resource res;
> +
> + np = of_find_compatible_node(NULL, NULL, "wrs,sbc8560-brstcr");
> + if (np == NULL) {
> + printk(KERN_WARNING "sbc8560: No board specific RSTCR in DTB.\n");
> + return -ENODEV;
> + }
> +
> + of_address_to_resource(np, 0, &res);
> +
> + printk(KERN_INFO "sbc8560: Found BRSTCR at i/o 0x%x\n", res.start);
> +
> + brstcr = ioremap(res.start, res.end - res.start);
> + if(!brstcr)
> + printk(KERN_WARNING "sbc8560: ioremap of brstcr failed.\n");
> +
> + of_node_put(np);
> +
> + return 0;
> +}
> +
> +arch_initcall(sbc8560_bdrstcr_init);
> +
> +void sbc8560_rstcr_restart(char * cmd)
> +{
> + local_irq_disable();
> + if(brstcr)
> + out_8(brstcr,in_8(brstcr) & 0x7f);
how about using clrbits8()
> +
> + while(1);
> +}
> +
> define_machine(sbc8560) {
> .name = "SBC8560",
> .probe = sbc8560_probe,
> @@ -274,7 +311,7 @@ define_machine(sbc8560) {
> .init_IRQ = sbc8560_pic_init,
> .show_cpuinfo = sbc8560_show_cpuinfo,
> .get_irq = mpic_get_irq,
> - .restart = fsl_rstcr_restart,
> + .restart = sbc8560_rstcr_restart,
> .calibrate_decr = generic_calibrate_decr,
> .progress = udbg_progress,
> };
> --
> 1.6.3.3
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
^ permalink raw reply
* Re: [PATCH] sbc8560: Fix warm reboot with board specific reset function
From: Kumar Gala @ 2009-08-14 4:38 UTC (permalink / raw)
To: Paul Gortmaker; +Cc: linuxppc-dev
In-Reply-To: <1250204775-5001-1-git-send-email-paul.gortmaker@windriver.com>
On Aug 13, 2009, at 6:06 PM, Paul Gortmaker wrote:
> From: Liang Li <Liang.Li@windriver.com>
>
> The existing fsl_rstcr_restart function fails to reset the sbc8560
> board. This implements a board specific reset function that uses
> the RCR(Reset Control Register) of the board's EPLD to do a reset.
>
> Signed-off-by: Liang Li <Liang.Li@windriver.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
> arch/powerpc/platforms/85xx/sbc8560.c | 39 ++++++++++++++++++++++++
> ++++++++-
> 1 files changed, 38 insertions(+), 1 deletions(-)
The reason it didn't was that feature doesnt exist on the mpc8560 :)
- k
^ permalink raw reply
* [PATCH] sbc8560: Fix warm reboot with board specific reset function
From: Paul Gortmaker @ 2009-08-13 23:06 UTC (permalink / raw)
To: linuxppc-dev
From: Liang Li <Liang.Li@windriver.com>
The existing fsl_rstcr_restart function fails to reset the sbc8560
board. This implements a board specific reset function that uses
the RCR(Reset Control Register) of the board's EPLD to do a reset.
Signed-off-by: Liang Li <Liang.Li@windriver.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
arch/powerpc/platforms/85xx/sbc8560.c | 39 ++++++++++++++++++++++++++++++++-
1 files changed, 38 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/platforms/85xx/sbc8560.c b/arch/powerpc/platforms/85xx/sbc8560.c
index cc27807..86dcca2 100644
--- a/arch/powerpc/platforms/85xx/sbc8560.c
+++ b/arch/powerpc/platforms/85xx/sbc8560.c
@@ -267,6 +267,43 @@ arch_initcall(sbc8560_rtc_init);
#endif /* M48T59 */
+static __u8 __iomem *brstcr;
+
+static int __init sbc8560_bdrstcr_init(void)
+{
+ struct device_node *np;
+ struct resource res;
+
+ np = of_find_compatible_node(NULL, NULL, "wrs,sbc8560-brstcr");
+ if (np == NULL) {
+ printk(KERN_WARNING "sbc8560: No board specific RSTCR in DTB.\n");
+ return -ENODEV;
+ }
+
+ of_address_to_resource(np, 0, &res);
+
+ printk(KERN_INFO "sbc8560: Found BRSTCR at i/o 0x%x\n", res.start);
+
+ brstcr = ioremap(res.start, res.end - res.start);
+ if(!brstcr)
+ printk(KERN_WARNING "sbc8560: ioremap of brstcr failed.\n");
+
+ of_node_put(np);
+
+ return 0;
+}
+
+arch_initcall(sbc8560_bdrstcr_init);
+
+void sbc8560_rstcr_restart(char * cmd)
+{
+ local_irq_disable();
+ if(brstcr)
+ out_8(brstcr,in_8(brstcr) & 0x7f);
+
+ while(1);
+}
+
define_machine(sbc8560) {
.name = "SBC8560",
.probe = sbc8560_probe,
@@ -274,7 +311,7 @@ define_machine(sbc8560) {
.init_IRQ = sbc8560_pic_init,
.show_cpuinfo = sbc8560_show_cpuinfo,
.get_irq = mpic_get_irq,
- .restart = fsl_rstcr_restart,
+ .restart = sbc8560_rstcr_restart,
.calibrate_decr = generic_calibrate_decr,
.progress = udbg_progress,
};
--
1.6.3.3
^ permalink raw reply related
* Re: [PATCH] powerpc: derive COMMAND_LINE_SIZE from asm-generic
From: Paul Gortmaker @ 2009-08-13 20:02 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: Linuxppc-dev
In-Reply-To: <200908131948.48103.arnd@arndb.de>
Arnd Bergmann wrote:
> On Thursday 13 August 2009 19:37:04 Paul Gortmaker wrote:
>> The default COMMAND_LINE_SIZE in asm-generic is 512, so the
>> net effect of this change is nil, aside from the cleanup
>> factor. See also commit 2b74b8569.
>>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> Just to clarify why this is good: There is a patch from Remis
> to kbuild that can automatically create the trivial wrappers,
> so we can remove arch/powerpc/include/asm/setup.h from the
> kernel once that patch is applied.
>
> I was also planning to submit a series to clean up more powerpc
> in this way headers where applicable, see
> http://git.kernel.org/?p=linux/kernel/git/arnd/asm-generic.git;a=shortlog;h=powerpc
I'd looked at master and next in your tree; I didn't
list all the branches and so I'd not noticed powerpc in there
as well.
>
> The series needs some forward porting to 2.6.31 as well as testing.
> If you or someone else wants to help with that, please go ahead!
I'll definitely have a look at what is in there.
Paul.
>
> Thanks,
>
> Arnd <><
^ permalink raw reply
* Re: [PATCH] powerpc: derive COMMAND_LINE_SIZE from asm-generic
From: Arnd Bergmann @ 2009-08-13 19:48 UTC (permalink / raw)
To: Paul Gortmaker; +Cc: Linuxppc-dev
In-Reply-To: <1250192224-22772-1-git-send-email-paul.gortmaker@windriver.com>
On Thursday 13 August 2009 19:37:04 Paul Gortmaker wrote:
> The default COMMAND_LINE_SIZE in asm-generic is 512, so the
> net effect of this change is nil, aside from the cleanup
> factor. See also commit 2b74b8569.
>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Just to clarify why this is good: There is a patch from Remis
to kbuild that can automatically create the trivial wrappers,
so we can remove arch/powerpc/include/asm/setup.h from the
kernel once that patch is applied.
I was also planning to submit a series to clean up more powerpc
in this way headers where applicable, see
http://git.kernel.org/?p=linux/kernel/git/arnd/asm-generic.git;a=shortlog;h=powerpc
The series needs some forward porting to 2.6.31 as well as testing.
If you or someone else wants to help with that, please go ahead!
Thanks,
Arnd <><
^ permalink raw reply
* [PATCH] powerpc: derive COMMAND_LINE_SIZE from asm-generic
From: Paul Gortmaker @ 2009-08-13 19:37 UTC (permalink / raw)
To: Linuxppc-dev; +Cc: arnd
The default COMMAND_LINE_SIZE in asm-generic is 512, so the
net effect of this change is nil, aside from the cleanup
factor. See also commit 2b74b8569.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
arch/powerpc/include/asm/setup.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/include/asm/setup.h b/arch/powerpc/include/asm/setup.h
index 817fac0..dae1934 100644
--- a/arch/powerpc/include/asm/setup.h
+++ b/arch/powerpc/include/asm/setup.h
@@ -1,6 +1,6 @@
#ifndef _ASM_POWERPC_SETUP_H
#define _ASM_POWERPC_SETUP_H
-#define COMMAND_LINE_SIZE 512
+#include <asm-generic/setup.h>
#endif /* _ASM_POWERPC_SETUP_H */
--
1.6.3.3
^ permalink raw reply related
* Re: Adding MTD concat support to FSL ELBC NAND driver
From: Scott Wood @ 2009-08-13 17:37 UTC (permalink / raw)
To: Felix Radensky; +Cc: linuxppc-dev@ozlabs.org list
In-Reply-To: <4A841933.8090808@embedded-sol.com>
Felix Radensky wrote:
> Currently concatenation support is implemented in physmap_of driver.
> The syntax used to define a concatenation device involves multiple
> reg tuples, as described in
> Documentation/powerpc/dts-bindings/mtd-physmap.txt. Will same syntax
> be acceptable for NAND chips ?
I'm not too fond of that -- it would require support in each controller
driver, and would preclude providing other device-specific information
in the node (e.g. what if each NAND chip has to sit under a different
parent node to describe its connection to the system?). What if a NAND
controller has multiple reg resources for each chip? It's not
memory-like the way NOR flash is.
If we're going to put it in the device tree at all (I suppose for the
same reason we put partitioning there), it should probably be some
external construct that glues together flash nodes.
-Scott
^ permalink raw reply
* Re: [PATCH 1/1 v1] powerpc44x: Add Eiger AMCC (AppliedMicro) PPC460SX evaluation board support.
From: Feng Kan @ 2009-08-13 17:34 UTC (permalink / raw)
To: Felix Radensky; +Cc: linuxppc-dev, Tai Tri Nguyen
In-Reply-To: <4A83AF5A.1040202@embedded-sol.com>
Hi Felix:
Sorry the documentation seems a little miss leading. There is no harm
with the bit
turned off to zero. Once the nand boot is over, we change the EBC to use
the ready
signal, this bit does not affect performance anymore.
Thanks
Feng Kan
On 08/12/2009 11:14 PM, Felix Radensky wrote:
> Hi,
>
> Feng Kan wrote:
>> This patch adds support for the AMCC (AppliedMicro) PPC460SX Eiger
>> evaluation board.
>>
>> Signed-off-by: Tai Tri Nguyen <ttnguyen@amcc.com>
>> Acked-by: Feng Kan <fkan@amcc.com>
>> Acked-by: Tirumala Marri <tmarri@amcc.com>
>> ---
>> arch/powerpc/boot/dts/eiger.dts | 421 ++++++++++
>> arch/powerpc/configs/44x/eiger_defconfig | 1200
>> ++++++++++++++++++++++++++++
>> arch/powerpc/platforms/44x/Kconfig | 12 +
>> arch/powerpc/platforms/44x/ppc44x_simple.c | 1 +
>> 4 files changed, 1634 insertions(+), 0 deletions(-)
>> create mode 100644 arch/powerpc/boot/dts/eiger.dts
>> create mode 100644 arch/powerpc/configs/44x/eiger_defconfig
>>
>> diff --git a/arch/powerpc/boot/dts/eiger.dts
>> b/arch/powerpc/boot/dts/eiger.dts
>> new file mode 100644
>> index 0000000..c4a934f
>> --- /dev/null
>> +++ b/arch/powerpc/boot/dts/eiger.dts
>> @@ -0,0 +1,421 @@
>> +/*
>> + * Device Tree Source for AMCC (AppliedMicro) Eiger(460SX)
>> + *
>> + * Copyright 2009 AMCC (AppliedMicro) <ttnguyen@amcc.com>
>> + *
>> + * This file is licensed under the terms of the GNU General Public
>> + * License version 2. This program is licensed "as is" without
>> + * any warranty of any kind, whether express or implied.
>> + */
>> +
>> +/dts-v1/;
>> +
>> +/ {
>> + #address-cells = <2>;
>> + #size-cells = <1>;
>> + model = "amcc,eiger";
>> + compatible = "amcc,eiger";
>> + dcr-parent = <&{/cpus/cpu@0}>;
>> +
>> + aliases {
>> + ethernet0 = &EMAC0;
>> + ethernet1 = &EMAC1;
>> + ethernet2 = &EMAC2;
>> + ethernet3 = &EMAC3;
>> + serial0 = &UART0;
>> + serial1 = &UART1;
>> + };
>> +
>> + cpus {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + cpu@0 {
>> + device_type = "cpu";
>> + model = "PowerPC,460SX";
>> + reg = <0x00000000>;
>> + clock-frequency = <0>; /* Filled in by U-Boot */
>> + timebase-frequency = <0>; /* Filled in by U-Boot */
>> + i-cache-line-size = <32>;
>> + d-cache-line-size = <32>;
>> + i-cache-size = <32768>;
>> + d-cache-size = <32768>;
>> + dcr-controller;
>> + dcr-access-method = "native";
>> + };
>> + };
>> +
>> + memory {
>> + device_type = "memory";
>> + reg = <0x00000000 0x00000000 0x00000000>; /* Filled in by
>> U-Boot */
>> + };
>> +
>> + UIC0: interrupt-controller0 {
>> + compatible = "ibm,uic-460sx","ibm,uic";
>> + interrupt-controller;
>> + cell-index = <0>;
>> + dcr-reg = <0x0c0 0x009>;
>> + #address-cells = <0>;
>> + #size-cells = <0>;
>> + #interrupt-cells = <2>;
>> + };
>> +
>> + UIC1: interrupt-controller1 {
>> + compatible = "ibm,uic-460sx","ibm,uic";
>> + interrupt-controller;
>> + cell-index = <1>;
>> + dcr-reg = <0x0d0 0x009>;
>> + #address-cells = <0>;
>> + #size-cells = <0>;
>> + #interrupt-cells = <2>;
>> + interrupts = <0x1e 0x4 0x1f 0x4>; /* cascade */
>> + interrupt-parent = <&UIC0>;
>> + };
>> +
>> + UIC2: interrupt-controller2 {
>> + compatible = "ibm,uic-460sx","ibm,uic";
>> + interrupt-controller;
>> + cell-index = <2>;
>> + dcr-reg = <0x0e0 0x009>;
>> + #address-cells = <0>;
>> + #size-cells = <0>;
>> + #interrupt-cells = <2>;
>> + interrupts = <0xa 0x4 0xb 0x4>; /* cascade */
>> + interrupt-parent = <&UIC0>;
>> + };
>> +
>> + UIC3: interrupt-controller3 {
>> + compatible = "ibm,uic-460sx","ibm,uic";
>> + interrupt-controller;
>> + cell-index = <3>;
>> + dcr-reg = <0x0f0 0x009>;
>> + #address-cells = <0>;
>> + #size-cells = <0>;
>> + #interrupt-cells = <2>;
>> + interrupts = <0x10 0x4 0x11 0x4>; /* cascade */
>> + interrupt-parent = <&UIC0>;
>> + };
>> +
>> + SDR0: sdr {
>> + compatible = "ibm,sdr-460sx";
>> + dcr-reg = <0x00e 0x002>;
>> + };
>> +
>> + CPR0: cpr {
>> + compatible = "ibm,cpr-460sx";
>> + dcr-reg = <0x00c 0x002>;
>> + };
>> +
>> + plb {
>> + compatible = "ibm,plb-460sx", "ibm,plb4";
>> + #address-cells = <2>;
>> + #size-cells = <1>;
>> + ranges;
>> + clock-frequency = <0>; /* Filled in by U-Boot */
>> +
>> + SDRAM0: sdram {
>> + compatible = "ibm,sdram-460sx", "ibm,sdram-405gp";
>> + dcr-reg = <0x010 0x002>;
>> + };
>> +
>> + MAL0: mcmal {
>> + compatible = "ibm,mcmal-460sx", "ibm,mcmal2";
>> + dcr-reg = <0x180 0x62>;
>> + num-tx-chans = <4>;
>> + num-rx-chans = <32>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + interrupt-parent = <&UIC1>;
>> + interrupts = < /*TXEOB*/ 0x6 0x4
>> + /*RXEOB*/ 0x7 0x4
>> + /*SERR*/ 0x1 0x4
>> + /*TXDE*/ 0x2 0x4
>> + /*RXDE*/ 0x3 0x4
>> + /*COAL TX0*/ 0x18 0x2
>> + /*COAL TX1*/ 0x19 0x2
>> + /*COAL TX2*/ 0x1a 0x2
>> + /*COAL TX3*/ 0x1b 0x2
>> + /*COAL RX0*/ 0x1c 0x2
>> + /*COAL RX1*/ 0x1d 0x2
>> + /*COAL RX2*/ 0x1e 0x2
>> + /*COAL RX3*/ 0x1f 0x2>;
>> + };
>> +
>> + POB0: opb {
>> + compatible = "ibm,opb-460sx", "ibm,opb";
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + ranges = <0xb0000000 0x00000004 0xb0000000 0x50000000>;
>> + clock-frequency = <0>; /* Filled in by U-Boot */
>> +
>> + EBC0: ebc {
>> + compatible = "ibm,ebc-460sx", "ibm,ebc";
>> + dcr-reg = <0x012 0x002>;
>> + #address-cells = <2>;
>> + #size-cells = <1>;
>> + clock-frequency = <0>; /* Filled in by U-Boot */
>> + /* ranges property is supplied by U-Boot */
>> + interrupts = <0x6 0x4>;
>> + interrupt-parent = <&UIC1>;
>> +
>> + nor_flash@0,0 {
>> + compatible = "amd,s29gl512n", "cfi-flash";
>> + bank-width = <2>;
>> + /* reg property is supplied in by U-Boot */
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + partition@0 {
>> + label = "kernel";
>> + reg = <0x00000000 0x001e0000>;
>> + };
>> + partition@1e0000 {
>> + label = "dtb";
>> + reg = <0x001e0000 0x00020000>;
>> + };
>> + partition@200000 {
>> + label = "ramdisk";
>> + reg = <0x00200000 0x01400000>;
>> + };
>> + partition@1600000 {
>> + label = "jffs2";
>> + reg = <0x01600000 0x00400000>;
>> + };
>> + partition@1a00000 {
>> + label = "user";
>> + reg = <0x01a00000 0x02560000>;
>> + };
>> + partition@3f60000 {
>> + label = "env";
>> + reg = <0x03f60000 0x00040000>;
>> + };
>> + partition@3fa0000 {
>> + label = "u-boot";
>> + reg = <0x03fa0000 0x00060000>;
>> + };
>> + };
>> +
>> + ndfc@1,0 {
>> + compatible = "ibm,ndfc";
>> + /* reg property is supplied by U-boot */
>> + ccr = <0x00003000>;
>
> Why don't you set EBCC bit in CCR ? It seems to be required for normal
> operation.
>
>
>> + bank-settings = <0x80002222>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> + nand {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + partition@0 {
>> + label = "uboot";
>> + reg = <0x00000000 0x00200000>;
>> + };
>> + partition@200000 {
>> + label = "uboot-environment";
>> + reg = <0x00200000 0x00100000>;
>> + };
>> + partition@300000 {
>> + label = "linux";
>> + reg = <0x00300000 0x00300000>;
>> + };
>> + partition@600000 {
>> + label = "root-file-system";
>> + reg = <0x00600000 0x01900000>;
>> + };
>> + partition@1f00000 {
>> + label = "device-tree";
>> + reg = <0x01f00000 0x00020000>;
>> + };
>> + partition@1f20000 {
>> + label = "data";
>> + reg = <0x01f20000 0x060E0000>;
>> + };
>> + };
>> + };
>> + };
>> +
>
> Felix.
^ permalink raw reply
* Re: [PATCH] Add kmemleak annotations to lmb.c
From: Catalin Marinas @ 2009-08-13 15:40 UTC (permalink / raw)
To: Michael Ellerman; +Cc: linuxppc-dev, David S. Miller
In-Reply-To: <e846103b117cc36798b1f352ed526d600fd88e16.1250132460.git.michael@ellerman.id.au>
On Thu, 2009-08-13 at 13:01 +1000, Michael Ellerman wrote:
> We don't actually want kmemleak to track the lmb allocations, so we
> pass min_count as 0. However telling kmemleak about lmb allocations
> allows it to scan that memory for pointers to other memory that is
> tracked by kmemleak, ie. slab allocations etc.
Looks alright to me (though I haven't tested it). You can add a
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
--
Catalin
^ permalink raw reply
* [PATCH 2/2] powerpc/44x: Update Arches defconfig
From: Stefan Roese @ 2009-08-13 14:30 UTC (permalink / raw)
To: linuxppc-dev
This patch adds NOR MTD support and I2C HWMON support for the AD7414
to the AMCC Arches defconfig.
Signed-off-by: Stefan Roese <sr@denx.de>
---
arch/powerpc/configs/44x/arches_defconfig | 382 +++++++++++++++++++++++++----
1 files changed, 332 insertions(+), 50 deletions(-)
diff --git a/arch/powerpc/configs/44x/arches_defconfig b/arch/powerpc/configs/44x/arches_defconfig
index f7fd32c..6f976b5 100644
--- a/arch/powerpc/configs/44x/arches_defconfig
+++ b/arch/powerpc/configs/44x/arches_defconfig
@@ -1,14 +1,14 @@
#
# Automatically generated make config: don't edit
-# Linux kernel version: 2.6.29-rc2
-# Tue Jan 20 08:22:31 2009
+# Linux kernel version: 2.6.31-rc5
+# Thu Aug 13 14:14:07 2009
#
# CONFIG_PPC64 is not set
#
# Processor support
#
-# CONFIG_6xx is not set
+# CONFIG_PPC_BOOK3S_32 is not set
# CONFIG_PPC_85xx is not set
# CONFIG_PPC_8xx is not set
# CONFIG_40x is not set
@@ -31,15 +31,16 @@ CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_HARDIRQS=y
+CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_IRQ_PER_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
+CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_ILOG2_U32=y
CONFIG_GENERIC_HWEIGHT=y
-CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
# CONFIG_ARCH_NO_VIRT_TO_BUS is not set
CONFIG_PPC=y
@@ -53,11 +54,14 @@ CONFIG_PPC_UDBG_16550=y
# CONFIG_GENERIC_TBSYNC is not set
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
+CONFIG_DTC=y
# CONFIG_DEFAULT_UIMAGE is not set
CONFIG_PPC_DCR_NATIVE=y
# CONFIG_PPC_DCR_MMIO is not set
CONFIG_PPC_DCR=y
+CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
+CONFIG_CONSTRUCTORS=y
#
# General setup
@@ -71,9 +75,19 @@ CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
+CONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
+
+#
+# RCU Subsystem
+#
+CONFIG_CLASSIC_RCU=y
+# CONFIG_TREE_RCU is not set
+# CONFIG_PREEMPT_RCU is not set
+# CONFIG_TREE_RCU_TRACE is not set
+# CONFIG_PREEMPT_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_GROUP_SCHED is not set
@@ -84,8 +98,12 @@ CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
+CONFIG_RD_GZIP=y
+# CONFIG_RD_BZIP2 is not set
+# CONFIG_RD_LZMA is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
+CONFIG_ANON_INODES=y
CONFIG_EMBEDDED=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
@@ -95,23 +113,30 @@ CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
-CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
-CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
+CONFIG_HAVE_PERF_COUNTERS=y
+
+#
+# Performance Counters
+#
+# CONFIG_PERF_COUNTERS is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
+# CONFIG_STRIP_ASM_SYMS is not set
+CONFIG_COMPAT_BRK=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
+# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
@@ -119,6 +144,12 @@ CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
+
+#
+# GCOV-based kernel profiling
+#
+# CONFIG_GCOV_KERNEL is not set
+# CONFIG_SLOW_WORK is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
@@ -130,8 +161,7 @@ CONFIG_MODULE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_BLOCK=y
-CONFIG_LBD=y
-# CONFIG_BLK_DEV_IO_TRACE is not set
+CONFIG_LBDAF=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
@@ -147,11 +177,6 @@ CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
-CONFIG_CLASSIC_RCU=y
-# CONFIG_TREE_RCU is not set
-# CONFIG_PREEMPT_RCU is not set
-# CONFIG_TREE_RCU_TRACE is not set
-# CONFIG_PREEMPT_RCU_TRACE is not set
# CONFIG_FREEZER is not set
CONFIG_PPC4xx_PCI_EXPRESS=y
@@ -172,6 +197,7 @@ CONFIG_PPC4xx_PCI_EXPRESS=y
CONFIG_ARCHES=y
# CONFIG_CANYONLANDS is not set
# CONFIG_GLACIER is not set
+# CONFIG_REDWOOD is not set
# CONFIG_YOSEMITE is not set
# CONFIG_XILINX_VIRTEX440_GENERIC_BOARD is not set
CONFIG_PPC44x_SIMPLE=y
@@ -214,6 +240,7 @@ CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_IOMMU_HELPER is not set
+# CONFIG_SWIOTLB is not set
CONFIG_PPC_NEED_DMA_SYNC_OPS=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_HAS_WALK_MEMORY=y
@@ -233,10 +260,14 @@ CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
-CONFIG_UNEVICTABLE_LRU=y
+CONFIG_HAVE_MLOCK=y
+CONFIG_HAVE_MLOCKED_PAGE_BIT=y
+CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
+CONFIG_STDBINUTILS=y
CONFIG_PPC_4K_PAGES=y
# CONFIG_PPC_16K_PAGES is not set
# CONFIG_PPC_64K_PAGES is not set
+# CONFIG_PPC_256K_PAGES is not set
CONFIG_FORCE_MAX_ZONEORDER=11
CONFIG_PROC_DEVICETREE=y
CONFIG_CMDLINE_BOOL=y
@@ -261,6 +292,7 @@ CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_LEGACY is not set
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
+# CONFIG_PCI_IOV is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_HAS_RAPIDIO is not set
@@ -278,14 +310,12 @@ CONFIG_PAGE_OFFSET=0xc0000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_PHYSICAL_START=0x00000000
CONFIG_TASK_SIZE=0xc0000000
-CONFIG_CONSISTENT_START=0xff100000
CONFIG_CONSISTENT_SIZE=0x00200000
CONFIG_NET=y
#
# Networking options
#
-CONFIG_COMPAT_NET_DEV_OPS=y
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
@@ -335,6 +365,8 @@ CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
+# CONFIG_PHONET is not set
+# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
@@ -347,7 +379,6 @@ CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
-# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
@@ -371,8 +402,92 @@ CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
-# CONFIG_MTD is not set
+CONFIG_MTD=y
+# CONFIG_MTD_DEBUG is not set
+# CONFIG_MTD_CONCAT is not set
+CONFIG_MTD_PARTITIONS=y
+# CONFIG_MTD_TESTS is not set
+# CONFIG_MTD_REDBOOT_PARTS is not set
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_OF_PARTS=y
+# CONFIG_MTD_AR7_PARTS is not set
+
+#
+# User Modules And Translation Layers
+#
+CONFIG_MTD_CHAR=y
+CONFIG_MTD_BLKDEVS=y
+CONFIG_MTD_BLOCK=y
+# CONFIG_FTL is not set
+# CONFIG_NFTL is not set
+# CONFIG_INFTL is not set
+# CONFIG_RFD_FTL is not set
+# CONFIG_SSFDC is not set
+# CONFIG_MTD_OOPS is not set
+
+#
+# RAM/ROM/Flash chip drivers
+#
+CONFIG_MTD_CFI=y
+# CONFIG_MTD_JEDECPROBE is not set
+CONFIG_MTD_GEN_PROBE=y
+# CONFIG_MTD_CFI_ADV_OPTIONS is not set
+CONFIG_MTD_MAP_BANK_WIDTH_1=y
+CONFIG_MTD_MAP_BANK_WIDTH_2=y
+CONFIG_MTD_MAP_BANK_WIDTH_4=y
+# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
+# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
+# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
+CONFIG_MTD_CFI_I1=y
+CONFIG_MTD_CFI_I2=y
+# CONFIG_MTD_CFI_I4 is not set
+# CONFIG_MTD_CFI_I8 is not set
+# CONFIG_MTD_CFI_INTELEXT is not set
+CONFIG_MTD_CFI_AMDSTD=y
+# CONFIG_MTD_CFI_STAA is not set
+CONFIG_MTD_CFI_UTIL=y
+# CONFIG_MTD_RAM is not set
+# CONFIG_MTD_ROM is not set
+# CONFIG_MTD_ABSENT is not set
+
+#
+# Mapping drivers for chip access
+#
+# CONFIG_MTD_COMPLEX_MAPPINGS is not set
+# CONFIG_MTD_PHYSMAP is not set
+CONFIG_MTD_PHYSMAP_OF=y
+# CONFIG_MTD_INTEL_VR_NOR is not set
+# CONFIG_MTD_PLATRAM is not set
+
+#
+# Self-contained MTD device drivers
+#
+# CONFIG_MTD_PMC551 is not set
+# CONFIG_MTD_SLRAM is not set
+# CONFIG_MTD_PHRAM is not set
+# CONFIG_MTD_MTDRAM is not set
+# CONFIG_MTD_BLOCK2MTD is not set
+
+#
+# Disk-On-Chip Device Drivers
+#
+# CONFIG_MTD_DOC2000 is not set
+# CONFIG_MTD_DOC2001 is not set
+# CONFIG_MTD_DOC2001PLUS is not set
+# CONFIG_MTD_NAND is not set
+# CONFIG_MTD_ONENAND is not set
+
+#
+# LPDDR flash memory drivers
+#
+# CONFIG_MTD_LPDDR is not set
+
+#
+# UBI - Unsorted block images
+#
+# CONFIG_MTD_UBI is not set
CONFIG_OF_DEVICE=y
+CONFIG_OF_I2C=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
@@ -412,7 +527,11 @@ CONFIG_HAVE_IDE=y
#
#
-# Enable only one of the two stacks, unless you know what you are doing
+# You can enable one or both FireWire driver stacks.
+#
+
+#
+# See the help texts for more information.
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
@@ -433,6 +552,8 @@ CONFIG_NET_ETHERNET=y
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
+# CONFIG_ETHOC is not set
+# CONFIG_DNET is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_IBM_NEW_EMAC=y
@@ -451,6 +572,7 @@ CONFIG_IBM_NEW_EMAC_EMAC4=y
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
# CONFIG_NET_PCI is not set
# CONFIG_B44 is not set
+# CONFIG_KS8842 is not set
# CONFIG_ATL2 is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
@@ -461,7 +583,6 @@ CONFIG_IBM_NEW_EMAC_EMAC4=y
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
-# CONFIG_IWLWIFI_LEDS is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
@@ -533,13 +654,143 @@ CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
-# CONFIG_I2C is not set
+CONFIG_I2C=y
+CONFIG_I2C_BOARDINFO=y
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_HELPER_AUTO=y
+
+#
+# I2C Hardware Bus support
+#
+
+#
+# PC SMBus host controller drivers
+#
+# CONFIG_I2C_ALI1535 is not set
+# CONFIG_I2C_ALI1563 is not set
+# CONFIG_I2C_ALI15X3 is not set
+# CONFIG_I2C_AMD756 is not set
+# CONFIG_I2C_AMD8111 is not set
+# CONFIG_I2C_I801 is not set
+# CONFIG_I2C_ISCH is not set
+# CONFIG_I2C_PIIX4 is not set
+# CONFIG_I2C_NFORCE2 is not set
+# CONFIG_I2C_SIS5595 is not set
+# CONFIG_I2C_SIS630 is not set
+# CONFIG_I2C_SIS96X is not set
+# CONFIG_I2C_VIA is not set
+# CONFIG_I2C_VIAPRO is not set
+
+#
+# I2C system bus drivers (mostly embedded / system-on-chip)
+#
+CONFIG_I2C_IBM_IIC=y
+# CONFIG_I2C_MPC is not set
+# CONFIG_I2C_OCORES is not set
+# CONFIG_I2C_SIMTEC is not set
+
+#
+# External I2C/SMBus adapter drivers
+#
+# CONFIG_I2C_PARPORT_LIGHT is not set
+# CONFIG_I2C_TAOS_EVM is not set
+
+#
+# Graphics adapter I2C/DDC channel drivers
+#
+# CONFIG_I2C_VOODOO3 is not set
+
+#
+# Other I2C/SMBus bus drivers
+#
+# CONFIG_I2C_PCA_PLATFORM is not set
+# CONFIG_I2C_STUB is not set
+
+#
+# Miscellaneous I2C Chip support
+#
+# CONFIG_DS1682 is not set
+# CONFIG_SENSORS_PCF8574 is not set
+# CONFIG_PCF8575 is not set
+# CONFIG_SENSORS_PCA9539 is not set
+# CONFIG_SENSORS_TSL2550 is not set
+# CONFIG_I2C_DEBUG_CORE is not set
+# CONFIG_I2C_DEBUG_ALGO is not set
+# CONFIG_I2C_DEBUG_BUS is not set
+# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
+
+#
+# PPS support
+#
+# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
-# CONFIG_HWMON is not set
+CONFIG_HWMON=y
+# CONFIG_HWMON_VID is not set
+CONFIG_SENSORS_AD7414=y
+# CONFIG_SENSORS_AD7418 is not set
+# CONFIG_SENSORS_ADM1021 is not set
+# CONFIG_SENSORS_ADM1025 is not set
+# CONFIG_SENSORS_ADM1026 is not set
+# CONFIG_SENSORS_ADM1029 is not set
+# CONFIG_SENSORS_ADM1031 is not set
+# CONFIG_SENSORS_ADM9240 is not set
+# CONFIG_SENSORS_ADT7462 is not set
+# CONFIG_SENSORS_ADT7470 is not set
+# CONFIG_SENSORS_ADT7473 is not set
+# CONFIG_SENSORS_ADT7475 is not set
+# CONFIG_SENSORS_ATXP1 is not set
+# CONFIG_SENSORS_DS1621 is not set
+# CONFIG_SENSORS_I5K_AMB is not set
+# CONFIG_SENSORS_F71805F is not set
+# CONFIG_SENSORS_F71882FG is not set
+# CONFIG_SENSORS_F75375S is not set
+# CONFIG_SENSORS_G760A is not set
+# CONFIG_SENSORS_GL518SM is not set
+# CONFIG_SENSORS_GL520SM is not set
+# CONFIG_SENSORS_IT87 is not set
+# CONFIG_SENSORS_LM63 is not set
+# CONFIG_SENSORS_LM75 is not set
+# CONFIG_SENSORS_LM77 is not set
+# CONFIG_SENSORS_LM78 is not set
+# CONFIG_SENSORS_LM80 is not set
+# CONFIG_SENSORS_LM83 is not set
+# CONFIG_SENSORS_LM85 is not set
+# CONFIG_SENSORS_LM87 is not set
+# CONFIG_SENSORS_LM90 is not set
+# CONFIG_SENSORS_LM92 is not set
+# CONFIG_SENSORS_LM93 is not set
+# CONFIG_SENSORS_LTC4215 is not set
+# CONFIG_SENSORS_LTC4245 is not set
+# CONFIG_SENSORS_LM95241 is not set
+# CONFIG_SENSORS_MAX1619 is not set
+# CONFIG_SENSORS_MAX6650 is not set
+# CONFIG_SENSORS_PC87360 is not set
+# CONFIG_SENSORS_PC87427 is not set
+# CONFIG_SENSORS_PCF8591 is not set
+# CONFIG_SENSORS_SIS5595 is not set
+# CONFIG_SENSORS_DME1737 is not set
+# CONFIG_SENSORS_SMSC47M1 is not set
+# CONFIG_SENSORS_SMSC47M192 is not set
+# CONFIG_SENSORS_SMSC47B397 is not set
+# CONFIG_SENSORS_ADS7828 is not set
+# CONFIG_SENSORS_THMC50 is not set
+# CONFIG_SENSORS_TMP401 is not set
+# CONFIG_SENSORS_VIA686A is not set
+# CONFIG_SENSORS_VT1211 is not set
+# CONFIG_SENSORS_VT8231 is not set
+# CONFIG_SENSORS_W83781D is not set
+# CONFIG_SENSORS_W83791D is not set
+# CONFIG_SENSORS_W83792D is not set
+# CONFIG_SENSORS_W83793 is not set
+# CONFIG_SENSORS_W83L785TS is not set
+# CONFIG_SENSORS_W83L786NG is not set
+# CONFIG_SENSORS_W83627HF is not set
+# CONFIG_SENSORS_W83627EHF is not set
+# CONFIG_HWMON_DEBUG_CHIP is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
@@ -556,24 +807,15 @@ CONFIG_SSB_POSSIBLE=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
+# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_TMIO is not set
+# CONFIG_PMIC_DA903X is not set
+# CONFIG_MFD_WM8400 is not set
+# CONFIG_MFD_WM8350_I2C is not set
+# CONFIG_MFD_PCF50633 is not set
+# CONFIG_AB3100_CORE is not set
# CONFIG_REGULATOR is not set
-
-#
-# Multimedia devices
-#
-
-#
-# Multimedia core support
-#
-# CONFIG_VIDEO_DEV is not set
-# CONFIG_DVB_CORE is not set
-# CONFIG_VIDEO_MEDIA is not set
-
-#
-# Multimedia drivers
-#
-CONFIG_DAB=y
+# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
@@ -600,7 +842,12 @@ CONFIG_VIDEO_OUTPUT_CONTROL=m
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
+# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
+
+#
+# TI VLYNQ
+#
# CONFIG_STAGING is not set
#
@@ -614,11 +861,12 @@ CONFIG_EXT2_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
-CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
+CONFIG_FILE_LOCKING=y
+CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
@@ -628,6 +876,11 @@ CONFIG_INOTIFY_USER=y
# CONFIG_FUSE_FS is not set
#
+# Caches
+#
+# CONFIG_FSCACHE is not set
+
+#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
@@ -660,6 +913,17 @@ CONFIG_MISC_FILESYSTEMS=y
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
+CONFIG_JFFS2_FS=y
+CONFIG_JFFS2_FS_DEBUG=0
+CONFIG_JFFS2_FS_WRITEBUFFER=y
+# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
+# CONFIG_JFFS2_SUMMARY is not set
+# CONFIG_JFFS2_FS_XATTR is not set
+# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
+CONFIG_JFFS2_ZLIB=y
+# CONFIG_JFFS2_LZO is not set
+CONFIG_JFFS2_RTIME=y
+# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=y
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
@@ -670,6 +934,7 @@ CONFIG_CRAMFS=y
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
+# CONFIG_NILFS2_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
@@ -681,7 +946,6 @@ CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
-# CONFIG_SUNRPC_REGISTER_V4 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
@@ -697,6 +961,7 @@ CONFIG_SUNRPC=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_NLS is not set
# CONFIG_DLM is not set
+# CONFIG_BINARY_PRINTF is not set
#
# Library routines
@@ -711,11 +976,14 @@ CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
-CONFIG_PLIST=y
+CONFIG_ZLIB_DEFLATE=y
+CONFIG_DECOMPRESS_GZIP=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_HAVE_LMB=y
+CONFIG_NLATTR=y
+CONFIG_GENERIC_ATOMIC64=y
#
# Kernel hacking
@@ -733,6 +1001,9 @@ CONFIG_DEBUG_KERNEL=y
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
+CONFIG_DETECT_HUNG_TASK=y
+# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
+CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
@@ -743,6 +1014,9 @@ CONFIG_SCHED_DEBUG=y
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
+# CONFIG_DEBUG_LOCK_ALLOC is not set
+# CONFIG_PROVE_LOCKING is not set
+# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
@@ -754,7 +1028,6 @@ CONFIG_SCHED_DEBUG=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
-# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
@@ -762,27 +1035,36 @@ CONFIG_SCHED_DEBUG=y
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
+# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_HAVE_FUNCTION_TRACER=y
+CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
-
-#
-# Tracers
-#
+CONFIG_TRACING_SUPPORT=y
+CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
+# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
-# CONFIG_CONTEXT_SWITCH_TRACER is not set
+# CONFIG_ENABLE_DEFAULT_TRACERS is not set
# CONFIG_BOOT_TRACER is not set
-# CONFIG_TRACE_BRANCH_PROFILING is not set
+CONFIG_BRANCH_PROFILE_NONE=y
+# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
+# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
-# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
+# CONFIG_KMEMTRACE is not set
+# CONFIG_WORKQUEUE_TRACER is not set
+# CONFIG_BLK_DEV_IO_TRACE is not set
+# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
+# CONFIG_KMEMCHECK is not set
+# CONFIG_PPC_DISABLE_WERROR is not set
+CONFIG_PPC_WERROR=y
CONFIG_PRINT_STACK_DEPTH=64
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
-# CONFIG_DEBUG_PAGEALLOC is not set
+# CONFIG_PPC_EMULATED_STATS is not set
# CONFIG_CODE_PATCHING_SELFTEST is not set
# CONFIG_FTR_FIXUP_SELFTEST is not set
# CONFIG_MSI_BITMAP_SELFTEST is not set
--
1.6.3.4
^ permalink raw reply related
* [PATCH 1/2] powerpc/44x: Update Arches dts
From: Stefan Roese @ 2009-08-13 14:30 UTC (permalink / raw)
To: linuxppc-dev
This patch adds some nodes to the AMCC Arches dts:
- L2 cache support
- NOR FLASH mapping with default partitioning
- I2C HWMON device (AD7414)
Signed-off-by: Stefan Roese <sr@denx.de>
---
arch/powerpc/boot/dts/arches.dts | 50 ++++++++++++++++++++++++++++++++++++++
1 files changed, 50 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/boot/dts/arches.dts b/arch/powerpc/boot/dts/arches.dts
index d9113b1..414ef8b 100644
--- a/arch/powerpc/boot/dts/arches.dts
+++ b/arch/powerpc/boot/dts/arches.dts
@@ -124,6 +124,16 @@
dcr-reg = <0x00c 0x002>;
};
+ L2C0: l2c {
+ compatible = "ibm,l2-cache-460gt", "ibm,l2-cache";
+ dcr-reg = <0x020 0x008 /* Internal SRAM DCR's */
+ 0x030 0x008>; /* L2 cache DCR's */
+ cache-line-size = <32>; /* 32 bytes */
+ cache-size = <262144>; /* L2, 256K */
+ interrupt-parent = <&UIC1>;
+ interrupts = <11 1>;
+ };
+
plb {
compatible = "ibm,plb-460gt", "ibm,plb4";
#address-cells = <2>;
@@ -168,6 +178,38 @@
/* ranges property is supplied by U-Boot */
interrupts = <0x6 0x4>;
interrupt-parent = <&UIC1>;
+
+ nor_flash@0,0 {
+ compatible = "amd,s29gl256n", "cfi-flash";
+ bank-width = <2>;
+ reg = <0x00000000 0x00000000 0x02000000>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ partition@0 {
+ label = "kernel";
+ reg = <0x00000000 0x001e0000>;
+ };
+ partition@1e0000 {
+ label = "dtb";
+ reg = <0x001e0000 0x00020000>;
+ };
+ partition@200000 {
+ label = "root";
+ reg = <0x00200000 0x00200000>;
+ };
+ partition@400000 {
+ label = "user";
+ reg = <0x00400000 0x01b60000>;
+ };
+ partition@1f60000 {
+ label = "env";
+ reg = <0x01f60000 0x00040000>;
+ };
+ partition@1fa0000 {
+ label = "u-boot";
+ reg = <0x01fa0000 0x00060000>;
+ };
+ };
};
UART0: serial@ef600300 {
@@ -186,6 +228,14 @@
reg = <0xef600700 0x00000014>;
interrupt-parent = <&UIC0>;
interrupts = <0x2 0x4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ sttm@4a {
+ compatible = "ad,ad7414";
+ reg = <0x4a>;
+ interrupt-parent = <&UIC1>;
+ interrupts = <0x0 0x8>;
+ };
};
IIC1: i2c@ef600800 {
--
1.6.3.4
^ permalink raw reply related
* Adding MTD concat support to FSL ELBC NAND driver
From: Felix Radensky @ 2009-08-13 13:46 UTC (permalink / raw)
To: linuxppc-dev@ozlabs.org list, Scott Wood
Hi,
I'd like to be able to concatenate several NAND banks (each bank on
separate chip select)
into a single MTD device, and define partition table on a concatenated
device.
Currently concatenation support is implemented in physmap_of driver. The
syntax used
to define a concatenation device involves multiple reg tuples, as
described in
Documentation/powerpc/dts-bindings/mtd-physmap.txt. Will same syntax be
acceptable
for NAND chips ?
Thanks.
Felix.
^ permalink raw reply
* Re: [PATCH -v2 0/7] powerpc: use asm-generic/dma-mapping-common.h
From: Kumar Gala @ 2009-08-13 13:31 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: Linux-Kernel List, FUJITA Tomonori, Ingo Molnar, linuxppc-dev
In-Reply-To: <1250159900.24143.7.camel@pasglop>
On Aug 13, 2009, at 5:38 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2009-08-13 at 10:55 +0200, Ingo Molnar wrote:
>
>>> Or we can have the patches in core/iommu and I pull the whole
>>> thing in powerpc-next. [...]
>>
>> Ok! We could also stage it a bit (one or two weeks) in a separate
>> branch and allow a rebase, should you find any bugs during testing?
>
> Sounds like a plan.
>
> I'll try to sort that out tomorrow, I can stick them in my -test
> branch
> (which is rebase friendly) for a while too.
Getting them all in your -test branch gives Becky and I an opportunity
to test them w/all the other PPC changes on the platforms we have that
enable SWIOTLB today.
- k
^ permalink raw reply
* Re: [PATCH] viotape: Fix memory and semaphore leak
From: Michael Buesch @ 2009-08-13 13:18 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: Dave Boutcher, Ryan Arnold, linuxppc-dev, Colin Devilbiss
In-Reply-To: <1250139603.3587.106.camel@pasglop>
On Thursday 13 August 2009 07:00:03 Benjamin Herrenschmidt wrote:
> On Sat, 2009-07-18 at 15:06 +0200, Michael Buesch wrote:
> > This patch fixes a memory and semaphore leak in the viotape driver's
> > char device write op. It leaks the DMA memory and the semaphore lock
> > in case the device was opened with O_NONBLOCK.
> >
> > This patch is only compile tested, because I do not have the hardware.
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> (going trough my backlog ...)
>
> Thanks Michael, but I don't think that's right...
>
> IE. We aren't waiting for the write to complete, which means that it can
> be happening asynchronously, thus we must not free the DMA memory until
> it has actually complete.
>
> Now, if you look at vioHandleTapeEvent(), it does appear that when the
> completion happens, the DMA memory will eventually be released and the
> mutex up'ed.
>
> Or am I missing something ?
I think you are right.
--
Greetings, Michael.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox