Hi Linus !
Here are some late fixed for some freescale embedded platforms
for 2.6.35. A bit late but since it only touch their platform
code I don't really have an objection.
Cheers,
Ben.
The following changes since commit 1c5474a65bf15a4cb162dfff86d6d0b5a08a740c:
Linus Torvalds (1):
Hi Linus !
As discussed, here's the lmb rename to memblock.
CCing Russell since I know he has some patches in -next for using lmb on ARM
which
might need to be reworked on top of that.
BTW. There's another request coming your way for ppc stuff, it's not a
duplicate email :-)
Cheers,
Ben.
The
On 07/06/2010 07:06 AM, Rupjyoti Sarmah wrote:
This patch enables the on-chip DWC SATA controller of the AppliedMicro
processor 460EX.
Signed-off-by: Rupjyoti Sarmahrsar...@appliedmicro.com
Signed-off-by: Mark Miesfeldmmiesf...@appliedmicro.com
Signed-off-by: Prodyut
On Wed, 14 Jul 2010 12:25:03 +0900
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com wrote:
On Tue, 13 Jul 2010 22:18:03 -0500
Nathan Fontenot nf...@austin.ibm.com wrote:
On 07/13/2010 07:35 PM, KAMEZAWA Hiroyuki wrote:
On Tue, 13 Jul 2010 10:51:58 -0500
Nathan Fontenot
Hi Gurus,
Please give me some hints and directions to debug this problem. I've
been scratching my head for quite a while.
The problem is that after/when the kernel switches to the real console
from the boot console, printk() calls cpm_uart_console_write() to
print the first (?) message using the
+ if (prop)
+ prom_remove_property(node, prop);
+ prop = of_find_property(node, linux,devietree-end, NULL);
Either the indentation is wrong, or you're missing some braces here
You're missing a c as well (and a dash).
Segher
Hi all,
Currently the sdhci driver does everything in the atomic context.
And what is worse, PIO transfers are made from the IRQ handler.
This causes huge latencies (up to 120 ms). On some P2020 SOCs,
DMA and card detection is broken, which means that kernel polls
for the card via PIO transfers
There is no need for the timeout handler to run in the atomic
context, so this patch turns timeout timeout into the delayed
work.
Note that the timeout handler still grabs an irqsave spinlock,
we'll deal with it in a separate patch.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
The driver can happily live without an atomic context and tasklets,
so turn the tasklets into the work structs.
Tasklets handlers still grab irqsave spinlocks, but we'll deal
with it in a separate patch.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
drivers/mmc/host/sdhci.c | 48
There's no need to clear the interrupt status register bit-by-bit,
we can just clear it once. This simplifies irq handler.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
drivers/mmc/host/sdhci.c | 23 ++-
1 files changed, 6 insertions(+), 17 deletions(-)
diff
We only need atomic context to disable SDHCI interrupts, after that
we can run in a kernel thread.
Note that irq handler still grabs an irqsave spinlock, we'll deal
with it in a subsequent patch.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
drivers/mmc/host/sdhci.c | 47
Finally, we can get rid of the host-lock spinlock, and turn it
into a mutex.
This patch does just this.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
drivers/mmc/host/sdhci.c | 53 +++--
drivers/mmc/host/sdhci.h |3 +-
2 files changed, 24
Nowadays we can just call the card detection handler directly,
no need for the separate work struct.
We still need host-finish_work as sdhci_finish_work() calls
mmc_request_done(), which tries to re-enter the driver.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
Since we don't run in the atomic context any longer, we can
turn mdelay()s into msleep()s.
The only place where the driver is still using mdelay() is
sdhci_send_command(). There it is possible to use sleepable
delays too, but we don't actually want to force rescheduling
in a hot path.
Sure, we
Just a cosmetic change, should not affect functionality.
Signed-off-by: Anton Vorontsov avoront...@mvista.com
---
drivers/mmc/host/sdhci.c | 11 +--
1 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index e6adda8..c754df1
The config options for REDWOOD_[56] were commented out in the powerpc
Kconfig. The ifdefs referencing this options therefore are dead and all
references to this can be removed (Also dependencies in other KConfig
files).
Signed-off-by: Christian Dietrich qy03f...@stud.informatik.uni-erlangen.de
To build a proper flat device tree for kexec we need to know which
memreserve region was used for the device tree for the currently
running kernel, so we can remove it and replace it with the new
memreserve for the kexec'ed kernel
Signed-off-by: Matthew McClintock m...@freescale.com
---
V4: Fixed
V4: Fixed misspelling
Any particular reason you fixed only one of the two
mispelings I pointed out? (device tree is two words,
not one).
+ prop = of_find_property(node, linux,devicetree-start, NULL);
+ if (prop)
+ prom_remove_property(node, prop);
+
+ prop =
On Wed, 2010-07-14 at 17:35 +0200, Segher Boessenkool wrote:
V4: Fixed misspelling
Any particular reason you fixed only one of the two
mispelings I pointed out? (device tree is two words,
not one).
Ahh, my fault.
+ prop = of_find_property(node, linux,devicetree-start, NULL);
+
Any particular reason you fixed only one of the two
mispelings I pointed out? (device tree is two words,
not one).
Ahh, my fault.
Well I wasn't terribly clear ;-)
You could use one property instead of two; use addr+len
like every other property does.
You also should use a better name for
On Tue, Jul 13, 2010 at 10:47 PM, Grant Likely
grant.lik...@secretlab.ca wrote:
Okay, well I advocate for the -D /dev/null approach then. I think
that validating our defaults, and looking for the subtle interactions
are exactly what we want to be doing when it comes to defconfigs. The
fact
On Tue, 2010-07-13 at 20:07 -0400, Nicolas Pitre wrote:
That's one issue indeed.
But there is another issue that is somewhat related, which is to be able
to categorize config options.
Currently the defconfig files carry information about the proper driver
to enable in order to support
On 07/13/2010 10:26 PM, Dave Hansen wrote:
On Wed, 2010-07-14 at 09:35 +0900, KAMEZAWA Hiroyuki wrote:
2. I'd like to write a configfs module for handling memory hotplug even
when
sysfs directroy is not created.
Because configfs support rmdir/mkdir, the user (ppc's daemon?) has
While testing cpu offlining, we are regularly seeing the WARN_ON go off
in xics_ipi_dispatch. It can occur when an IPI gets sent to the CPU while
it is going offline. There is already a similar WARN_ON in the handlers
for PPC_MSG_CALL_FUNCTION and PPC_MSG_CALL_FUNC_SINGLE, so the warning
is not
Matthew McClintock wrote:
+static struct property flat_dt_start_prop = {
+ .name = linux,devicetree-start,
+ .length = sizeof(phys_addr_t),
+ .value =flat_dt_start,
+};
+
+static struct property flat_dt_end_prop = {
+ .name = linux,devicetree-end,
+ .length =
If the hypervisor gives us an error on a hugepage insert we panic. The
normal page code already handles this by returning an error instead and we end
calling low_hash_fault which will just kill the task if possible.
The patch below does a similar thing for the hugepage case.
Signed-off-by:
26 matches
Mail list logo