Thank you Mauro for the good explanation
Yeah, there are many changes there that justifies adding you at its
authorship, and that's ok. Also, anyone saying the size of your patch
will recognize your and ST efforts to improve the driver.
However, as some parts of the code were preserved,
As they are used from diff and event group report, add a test case to
verify their behaviors.
In this test I made a fake machine and two evsel. Each evsel got 10
samples (so hist entries) - 5 are common and the rests are not. So
after hists__match() both of them will have 5 entries with pair
On Wed, Dec 05, 2012 at 01:03:14PM +0100, Daniel Vetter wrote:
On Wed, Dec 5, 2012 at 12:47 PM, Terje Bergström tbergst...@nvidia.com
wrote:
You're right in that binding to a sub-device is not a nice way. DRM
framework just needs a struct device to bind to. exynos seems to solve
this by
On Wed, Dec 5, 2012 at 1:22 PM, Thierry Reding
thierry.red...@avionic-design.de wrote:
Maybe something more elaborate could help, though. Suppose we add
functionality to DRM to instantiate a DRM device. We could call such a
function from the host1x driver to add a device which the tegra-drm
Hi!
Agreed. If I understand you correctly though, your approach is specific
to a particular hardware implementation (Zynq) on the user interface layer,
which I think is exactly what we should avoid. Obviously, there is
always a driver involved that is specific to the IP block you load into
Takashi Iwai ti...@suse.de wrote:
From: Takashi Iwai ti...@suse.de
Subject: [PATCH v2] MODSIGN: Avoid using .incbin in C source
Using the asm .incbin statement in C sources breaks any gcc wrapper which
assumes that preprocessed C source is self-contained. Use a separate .S
file to include
On 12/05/2012 03:40 AM, Andrew Morton wrote:
On Tue, 04 Dec 2012 14:23:41 +0530
Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com wrote:
From: Michael Wang wang...@linux.vnet.ibm.com
There are places where preempt_disable() is used to prevent any CPU from
going offline during the critical
On 12/05/2012 03:47 AM, Andrew Morton wrote:
On Tue, 04 Dec 2012 14:24:28 +0530
Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com wrote:
From: Michael Wang wang...@linux.vnet.ibm.com
With stop_machine() gone from the CPU offline path, we can't depend on
preempt_disable() to prevent CPUs
On Wed, Dec 05, 2012 at 12:08:12PM +0100, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The header of acpi_dev_pm_detach() in include/linux/acpi.h has an
incorrect return type, which should be void. Fix that.
Signed-off-by: Rafael J. Wysocki
On Wed, Dec 05, 2012 at 17:33:37, Nori, Sekhar wrote:
Hi Avinash,
On 11/29/2012 5:16 PM, Philip, Avinash wrote:
Update number of errors using nand ecc strength.
Also add macro definitions BCH8_ERROR_MAX BCH4_ERROR_MAX
Can you please describe why the original method of setting nerrors
On 12/05/2012 05:09 AM, Rusty Russell wrote:
Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com writes:
From: Michael Wang wang...@linux.vnet.ibm.com
With stop_machine() gone from the CPU offline path, we can't depend on
preempt_disable() to prevent CPUs from going offline from under us.
On Tuesday 04 December 2012 14:04:22 Mauro Carvalho Chehab wrote:
Em 24-09-2012 09:44, Marek Szyprowski escreveu:
Hello,
On Monday, September 24, 2012 12:59 PM Federico Vaga wrote:
The DMA streaming allocator is similar to the DMA contig but it use the
DMA streaming interface
I am deeply sorry.
I was busy first time I read this, so I postponed answering and ended up
forgetting.
Sorry
include/linux/sched.h:
unsigned long long run_delay; /* time spent waiting on a runqueue */
So if you are out of the runqueue, you won't get steal time accounted,
and then I truly
Hi!
I've seen the LTP open posix mmap/{11-4,11-5} issues in the past myself
and was something I wanted to discuss on the lists myself. Thanks for
bringing this up.
Jut to reiterate: the expectations are
1. zero filling of unmapped (trailing) partial page
2. NO Writeout (to disk) of
The root of problem is carelessly zeroing pointer(in function
__tty_buffer_flush()),
when another thread can use it. It can be cause of NULL pointer dereference.
Main idea of the patch, this is never free last (struct tty_buffer) in the
active buffer.
Only flush the data for
The i2c_device_id table is supposed to be zero-terminated.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/mfd/tps80031.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/tps80031.c b/drivers/mfd/tps80031.c
index f64005e..10b51f7 100644
--- a/drivers/mfd/tps80031.c
+++
Ping!!!
On 1 December 2012 00:33, Viresh Kumar viresh.ku...@linaro.org wrote:
On 30 November 2012 21:15, Lee Jones lee.jo...@linaro.org wrote:
But ... I don't see how the changes in the -i2c and -spi files
are of benefit either. When I boot without the ID table I still
get stmpe-i2c 0-0040:
Em 05-12-2012 10:24, Federico Vaga escreveu:
Thank you Mauro for the good explanation
Yeah, there are many changes there that justifies adding you at its
authorship, and that's ok. Also, anyone saying the size of your patch
will recognize your and ST efforts to improve the driver.
However, as
Dear Jan,
x86 debug registers are already very scarce. Besides that userland
applications know they have 4 of them available so it would also break
them.
If a userland application wants to cheat, then it has no need to bypass
the debug registers: even if there were 4096 of them, covering the
Ping!!!
Documentation/development-process/2.Process:
- Avoid top-posting (the practice of putting your answer above the quoted
text you are responding to). It makes your response harder to read and
makes a poor impression.
:)
On 1 December 2012 00:33, Viresh Kumar
This driver uses regmap_irq APIs, thus need to select REGMAP_IRQ.
IRQ_DOMAIN will be selected if select REGMAP_IRQ, thus remove it here.
This fixes below build errors:
drivers/built-in.o: In function `tps80031_remove':
drivers/mfd/tps80031.c:534: undefined reference to `regmap_del_irq_chip'
Ok, I understand. I will write something like this.
* Copyright (C) 2012 ST Microelectronics
* author: Federico Vaga federico.v...@gmail.com
* Copyright (C) 2010 WindRiver Systems, Inc.
* authors: Andreas Kies andreas.k...@windriver.com
*
On 5 December 2012 18:49, Lee Jones lee.jo...@linaro.org wrote:
Ping!!!
Documentation/development-process/2.Process:
- Avoid top-posting (the practice of putting your answer above the quoted
text you are responding to). It makes your response harder to read and
makes a poor impression.
On Wed, Dec 05, 2012 at 01:31:54PM +0100, Daniel Vetter wrote:
On Wed, Dec 5, 2012 at 1:22 PM, Thierry Reding
thierry.red...@avionic-design.de wrote:
Maybe something more elaborate could help, though. Suppose we add
functionality to DRM to instantiate a DRM device. We could call such a
Em 05-12-2012 11:27, Federico Vaga escreveu:
Ok, I understand. I will write something like this.
* Copyright (C) 2012 ST Microelectronics
* author: Federico Vaga federico.v...@gmail.com
* Copyright (C) 2010 WindRiver Systems, Inc.
* authors: Andreas Kies
Not sure if you got my point: the main point of removing MODULE_AUTHOR
and other copyright stuff is that such patch may easily be doing something
that could be considered a copyright violation, being bad not only to
the affected driver, but to the entire Kernel.
So, we need to handle it
File descriptors (even those for writing) do not hold freeze protection.
Thus mark_files_ro() must call __mnt_drop_write() to only drop protection
against remount read-only. Calling mnt_drop_write_file() as we do now
results in:
[ BUG: bad unlock balance detected! ]
3.7.0-rc6-00028-g88e75b6 #101
The %5lu part of the sprintf only guarantees a minimum length,
not a maximum one. This patch should make it correct for any
possible timestamp.
Signed-off-by: Sylvain Munaut s.mun...@whatever-company.com
---
kernel/printk.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
On Wed 05-12-12 02:36:44, azurIt wrote:
The following should print the traces when we hand over ENOMEM to the
caller. It should catch all charge paths (migration is not covered but
that one is not important here). If we don't see any traces from here
and there is still global OOM striking then
During some experiments with an external clock (in a FPGA), we saw that
the TSC clock drifted approx. 2.5ms per second.
This drift was caused by the current way of calculating the scale.
In our case cpu_khz had a value of 3292725. This resulted in a scale
value of 310. But when doing the
On 04/12/12 11:45, Dan Carpenter wrote:
I don't understand this, and I'm going to embarrass myself by
displaying my ignorance for all to see. Why is this code so
different from all the other 32 bit compat code that we have in the
kernel?
On Tue, Dec 04, 2012 at 10:44:14AM +, Serban
On 5 December 2012 00:04, Takashi Iwai ti...@suse.de wrote:
At Tue, 4 Dec 2012 23:54:39 +0800,
Daniel J Blueman wrote:
On 4 December 2012 23:03, Takashi Iwai ti...@suse.de wrote:
At Tue, 4 Dec 2012 22:46:47 +0800,
Daniel J Blueman wrote:
On 4 December 2012 21:55, Takashi Iwai
Em 05-12-2012 10:50, Federico Vaga escreveu:
On Tuesday 04 December 2012 14:04:22 Mauro Carvalho Chehab wrote:
Em 24-09-2012 09:44, Marek Szyprowski escreveu:
Hello,
On Monday, September 24, 2012 12:59 PM Federico Vaga wrote:
The DMA streaming allocator is similar to the DMA contig but it
On Wed, Dec 05, 2012 at 08:09:01AM +0100, Andreas Mohr wrote:
Hi,
drivers/pnp/pnpacpi/core.c: In function 'ispnpidacpi':
drivers/pnp/pnpacpi/core.c:65:2: warning: logical 'or' of collectively
exhaustive tests is always true [-Wlogical-op]
drivers/pnp/pnpacpi/core.c:66:2: warning: logical
This commit changes the CMA early initialization code to use phys_addr_t
for representing physical addresses instead of unsigned long.
Without this change, among other things, dma_declare_contiguous() simply
discards any memory regions whose address is not representable as unsigned
long.
This is
On 04/12/12 16:17, Greg KH wrote:
On Tue, Dec 04, 2012 at 10:44:13AM +, Serban Constantinescu wrote:
Android's IPC, Binder, does not support calls from a 32-bit userspace
in a 64 bit kernel. This patch adds support for syscalls coming from a
32-bit userspace in a 64-bit kernel.
Most of the
On Tue, Dec 04, 2012 at 02:03:12PM -0700, Lance Ortiz wrote:
This patch will provide a more reliable and easy way for user-space
applications to have access to AER logs rather than reading them from the
message buffer. It also provides a way to notify user-space when an AER
event occurs.
On Sun 02-12-12 01:40:28, Cong Ding wrote:
it's not necessary to lock the buffers because no one touches them
beyond the file system.
Although I agree those locks are not strictly necessary, I prefer to keep
them because the general rula is buffer contents should be changed under
buffer lock
Em Tue, 04 Dec 2012 14:03:18 -0700
Lance Ortiz lance.or...@hp.com escreveu:
Hmm... I did a reply to v6 of this patch, but i pressed the wrong button
and it went only to Joe. Excuse-me for that. Let me resend the
comments to everybody:
On Tue, 2012-12-04 at 16:33 -0200, Mauro Carvalho Chehab
On Tue, Dec 04, 2012 at 02:03:18PM -0700, Lance Ortiz wrote:
These changes make cper_print_aer more consistent with aer_print_error
which is called in the AER interrupt case. The string in the variable
'prefix' is printed at the beginning of each print statement in
cper_print_aer(). The prefix
On 05/12/12 00:26, Arve Hjønnevåg wrote:
On Tue, Dec 4, 2012 at 2:44 AM, Serban Constantinescu
serban.constantine...@arm.com wrote:
Android's IPC, Binder, does not support calls from a 32-bit userspace
in a 64 bit kernel. This patch adds support for syscalls coming from a
32-bit userspace in a
When printing, use a prefix of the PCI domain, bus, device and function
as in other drivers, to differentiate multiple devices.
Important for reporting and debugging. A future step is to tidy this up with
dev_printk et al.
v2: Move conversion specifier into call site, preventing build issues
v3:
On 12/04/2012 07:22 PM, David Miller :
From: Nicolas Ferre nicolas.fe...@atmel.com
Date: Mon, 3 Dec 2012 13:15:43 +0100
Macb Ethernet controller requires a RX buffer of 128 bytes. It is
highly sub-optimal for Gigabit-capable GEM that is able to use
a bigger DMA buffer. Change this constant
On Wed, Dec 05, 2012 at 02:31:02PM +, Serban Constantinescu wrote:
-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose the
At Wed, 5 Dec 2012 23:04:21 +0800,
Daniel J Blueman wrote:
When printing, use a prefix of the PCI domain, bus, device and function
as in other drivers, to differentiate multiple devices.
Important for reporting and debugging. A future step is to tidy this up with
dev_printk et al.
v2:
On 12/05/2012 10:35 AM, David Laight :
If I understand well, you mean that the call to:
dma_sync_single_range_for_device(bp-pdev-dev, phys,
pg_offset, frag_len, DMA_FROM_DEVICE);
in the rx path after having copied the data to skb is not needed?
That
On Wed, 5 Dec 2012 15:29:35 +0100
Borislav Petkov b...@alien8.de wrote:
On Wed, Dec 05, 2012 at 08:09:01AM +0100, Andreas Mohr wrote:
Hi,
drivers/pnp/pnpacpi/core.c: In function 'ispnpidacpi':
drivers/pnp/pnpacpi/core.c:65:2: warning: logical 'or' of collectively
exhaustive tests is
Well, for the 10/100 MACB interface, I am stuck with 128 Bytes buffers!
So this use of pages seems sensible.
If you have dma coherent memory you can make the rx buffer space
be an array of short buffers referenced by adjacent ring entries
(possibly with the last one slightly short to allow for
Unbinding an RTC chip driver from its device leads to the error
message:
|ida_remove called for id=0 which is not allocated.
This is caused by a redundant call to ida_simple_remove() in
rtc_device_unregister().
Eliminate the call in rtc_device_unregister() and only call the
function in
On Wed, Dec 05, 2012 at 03:27:56PM +, Alan Cox wrote:
On Wed, 5 Dec 2012 15:29:35 +0100
Borislav Petkov b...@alien8.de wrote:
On Wed, Dec 05, 2012 at 08:09:01AM +0100, Andreas Mohr wrote:
Hi,
drivers/pnp/pnpacpi/core.c: In function 'ispnpidacpi':
Hello.
We have several servers with mongodb running. Each server has several mongodb
instances. Mongodb dataset is larger then availiable memory (mongodb uses
memory-mapped files for all disk I/O).
2.6.32 and 2.6.38 kernels periodically crash and crash happens only with mongodb
servers.
On Tue 27-11-12 18:14:42, Marcus Sundman wrote:
On 22.11.2012 01:30, Jan Kara wrote:
On Fri 16-11-12 03:11:22, Marcus Sundman wrote:
On 13.11.2012 15:51, Jan Kara wrote:
On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
On 09.11.2012 01:41, Marcus Sundman wrote:
On 07.11.2012 18:17, Jan Kara
compiling the i.MX pwm driver produces the following warning:
|drivers/pwm/pwm-imx.c: In function 'imx_pwm_probe':
|drivers/pwm/pwm-imx.c:281:7: warning: assignment discards qualifiers from
pointer target type
Apply a 'const' attribute to the affected variable declaration.
Signed-off-by: Lothar
On 12/04/2012 06:34 PM, Bryan Wu wrote:
What's best thing I can do is I can merge these patchset into my
-devel branch, after 3.8 merge window close I will move this -devel
branch to my for-next branch for 3.9 merge window.
Does this make sense to you?
Not sure if I can get changes related
Hillarious!
Andrew, would you please pick up Alan's patch? It clearly fixes an
ancient bug in the pnpacpi code.
And yes btw we should turn this option on in -next, and get these sort of
things out of the tree for good. More importantly it'll mean anyone
adding another one gets a whine on the
On 05.12.2012 14:04, Thierry Reding wrote:
On Wed, Dec 05, 2012 at 01:47:38PM +0200, Terje Bergström wrote:
Yes, but there's more. For instance I went to great lengths to make sure
there's no global data whatsoever. So all the data is bound to the
host1x device in the current code. I know many
If we make movablecore_map take precedence over movablecore/kernelcore,
the logic could be simplified. I think it's not so attractive to support
both movablecore_map and movablecore/kernelcore at the same time.
On 11/23/2012 06:44 PM, Tang Chen wrote:
If kernelcore or movablecore is specified at
On Tue, Dec 04, 2012 at 08:43:18PM +, Arnd Bergmann wrote:
On Tuesday 04 December 2012, Eli Billauer wrote:
I'm currently writing some documentation which will cover the API and
also help reading the code, I hope. It takes some time...
Until it's done, let's look at a usage example:
On Wed, Dec 5, 2012 at 2:48 AM, Martin Steigerwald mar...@lichtvoll.de wrote:
Linus, while I am interested in an answer I think that Dave and Christoph
as Linux filesystem developers actually deserve one (instead of silently
being ignored which is also a decision in this matter).
I did not
On 11/23/2012 06:44 PM, Tang Chen wrote:
This patch introduces a new array zone_movable_limit[] to store the
ZONE_MOVABLE limit from movablecore_map boot option for all nodes.
The function sanitize_zone_movable_limit() will find out to which
node the ranges in movable_map.map[] belongs, and
On Wed, Dec 05, 2012 at 10:22:08PM +0700, Bokhan Artem wrote:
Hello.
We have several servers with mongodb running. Each server has
several mongodb instances. Mongodb dataset is larger then availiable
memory (mongodb uses memory-mapped files for all disk I/O).
2.6.32 and 2.6.38 kernels
On 05.12.2012 22:53, Borislav Petkov wrote:
On Wed, Dec 05, 2012 at 10:22:08PM +0700, Bokhan Artem wrote:
Hello.
We have several servers with mongodb running. Each server has
several mongodb instances. Mongodb dataset is larger then availiable
memory (mongodb uses memory-mapped files for all
Below is the list of build error/warning regressions/improvements in
v3.7-rc8[1] compared to v3.6[2].
To make this mail fit in the lkml limit, I deleted
- 6016 lines about __mcount_loc on sparc64
- all error and warning improvements
Summarized:
- build errors: +13/-952
- build warnings:
On Thu, Nov 29, 2012 at 04:46:05PM +0800, Lai Jiangshan wrote:
SRCU is based on its own statemachine and it doesn't
relies on normal RCU now, its read critical section can be used in
offline cpu, so we remove the check and the comments.
It partially reverts c0d6d01b(the part for SRCU).
It
On Wed, Dec 05, 2012 at 03:47:49PM +, Alan Cox wrote:
Hillarious!
Andrew, would you please pick up Alan's patch? It clearly fixes an
ancient bug in the pnpacpi code.
And yes btw we should turn this option on in -next, and get these sort of
things out of the tree for good. More
Dear RT Folks,
I'm pleased to announce the 3.6.9-rt21 release. 3.6.7-rt18, 3.6.8-rt19
and 3.6.9-rt20 are not announced updates to the respective 3.6.y
stable releases without any RT changes
Changes since 3.6.9-rt20:
* Fix the PREEMPT_LAZY implementation on ARM
* Fix the RCUTINY issues
Including asm/cacheflush.h from asm-generic/io.h prevents
cacheflush.h being able to use I/O functions like readl and writel due
to circular include dependencies. It doesn't appear as if anything from
cacheflush.h is actually used by the generic io.h, so remove the
include.
I've compile tested a
On 64 bit architectures with no efficient unaligned access, taskstats
has to add some padding to a reply to prevent unaligned access warnings.
However this also needs to apply to 32 bit architectures with 64 bit
struct alignment such as metag (which has 64 bit memory accesses).
This is solved by
The commit binfmt_elf: cleanups
(f670d0ecda73b7438eec9ed108680bc5f5362ad8) removed an ifndef elf_map but
this breaks compilation for metag which does define elf_map.
This adds the ifndef back in as it was before, but does not affect the
other cleanups made by that patch.
Signed-off-by: James
The powervr prefix which is currently described as Imagination
Technologies isn't really appropriate for non-PowerVR hardware, so
deprecate it, changing the description of powervr to PowerVR
(deprecated, use img), and add a separate img prefix for Imagination
Technologies Ltd..
Signed-off-by:
The ptrace interface for metag provides access to some core register
sets using the PTRACE_GETREGSET and PTRACE_SETREGSET operations. The
details of the internal context structures is abstracted into user API
structures to both ease use and allow flexibility to change the internal
context layouts.
Commit cc2383ec06be093789469852e1fe96e1148e9a2c (mm: introduce
arch-specific vma flag VM_ARCH_1) merged in v3.7-rc1.
The above commit combined several arch-specific vma flags into one, and
in the process it changed the VM_GROWSUP definition to depend on
specific architectures rather than
Add [!]METAG to various Kconfig dependencies in generic code, as
described below:
- Kconfig.debug: don't allow stack utilization instrumentation on
metag, and allow building with frame pointers.
- char: don't build rtc or genrtc on METAG
The metag architecture doesn't have a PC
Add the IMG Debug Adapter File System (DAFS) for metag, which uses
SWITCH operations to communicate with a file server on a host computer
via a JTAG debug adapter.
Signed-off-by: James Hogan james.ho...@imgtec.com
Cc: Alexander Viro v...@zeniv.linux.org.uk
Cc: linux-fsde...@vger.kernel.org
---
Add a TTY driver for communicating over a Meta DA (Debug Adapter)
channel using the bios channel SWITCH operation.
Signed-off-by: James Hogan james.ho...@imgtec.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
---
MAINTAINERS|1 +
arch/metag/Kconfig
Add basic JTAG Debug Adapter (DA) support so that drivers which
communicate with the DA can detect whether one is actually present
(otherwise the target will halt indefinitely).
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/Kconfig |9 ++
Add oprofile support for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/Kconfig|1 +
arch/metag/Makefile |2 +
arch/metag/oprofile/Makefile | 16 ++
arch/metag/oprofile/backtrace.c | 134 ++
Adapt checkstack.pl so that it works for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
scripts/checkstack.pl |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/scripts/checkstack.pl b/scripts/checkstack.pl
index 17e3843..544aa56 100755
---
Add Perf support for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/Kconfig |1 +
arch/metag/include/asm/perf_event.h |4 +
arch/metag/kernel/Makefile |2 +
arch/metag/kernel/perf/Makefile |3 +
Add family 16h PCI ID to AMD's power driver to allow it report
power consumption on these processors.
Signed-off-by: Boris Ostrovsky boris.ostrov...@amd.com
---
drivers/hwmon/fam15h_power.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/hwmon/fam15h_power.c
Add metag build infrastructure.
TODO: use generic CMDLINE Kconfig symbols
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/Kconfig | 299
arch/metag/Kconfig.debug | 40 +
arch/metag/Kconfig.soc
Add time keeping code for metag. Meta hardware threads have 2 timers.
The background timer (TXTIMER) is used as a free-running time base, and
the interrupt timer (TXTIMERI) is used for the timer interrupt. Both
counters traditionally count at approximately 1MHz.
Signed-off-by: James Hogan
Add device tree files to arch/metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/boot/dtb/Makefile | 17 ++
arch/metag/boot/dts/skeleton.dts | 10
arch/metag/boot/dts/skeleton.dtsi | 14 +
arch/metag/include/asm/prom.h | 23 +
Add ftrace support for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/Kconfig |5 ++
arch/metag/include/asm/Kbuild |1 -
arch/metag/include/asm/ftrace.h | 23 +++
arch/metag/kernel/ftrace.c | 127 +++
Hi Peter,
Thanks for your contribution.
I have modified the driver files name and descriptions.
Regarding the warnings, it's strange.
@Kent, could you confirm that you have the same?
Regards,
Mathias Leblanc
-Original Message-
From: Peter Hüwe [mailto:peterhu...@gmx.de]
Sent: 29
Add the remaining metag header files:
- byteorder.h, swab.h (byte order and swapping)
- barrier.h, cpu.h. hwthread.h, processor.h (hardware thread related)
- bug.h, elf.h, gpio.h, linkage.h, resource.h (other)
Signed-off-by: James Hogan james.ho...@imgtec.com
---
Add stack unwinding support for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/asm/stacktrace.h | 20
arch/metag/kernel/stacktrace.c | 187 +++
2 files changed, 207 insertions(+), 0 deletions(-)
create mode 100644
Add DMA mapping code.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/asm/dma-mapping.h | 183
arch/metag/kernel/dma.c | 507 ++
2 files changed, 690 insertions(+), 0 deletions(-)
create mode 100644
Add SMP support for metag. This allows Linux to take control of multiple
hardware threads on a single Meta core, treating them as separate Linux
CPUs.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/asm/cachepart.h | 42 +++
arch/metag/include/asm/core_reg.h |7 +
Add basic metag documentation.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
Documentation/00-INDEX |2 ++
Documentation/kernel-parameters.txt |4
Documentation/metag/00-INDEX|2 ++
3 files changed, 8 insertions(+), 0 deletions(-)
create mode 100644
+ char *prefix = NULL;
What are you doing here? You dropped the 'prefix' argument being passed
down in this function and are defining a local variable of the same
name
which is used in the function later:
printk(%saer_status: 0x%08x, aer_mask: 0x%08x\n,
prefix,
Add header files to implement Meta hardware thread locks (used by some
other atomic operations), atomics, spinlocks, and bitops.
There are 2 main types of atomic primitives for metag (in addition to
IRQs off on UP):
- LOCK instructions provide locking between hardware threads.
- LNKGET/LNKSET
On 12/03/2012 06:41 PM, Peter Hurley wrote:
The lock logic for tty_set_ldisc() is wrong. Despite existing code in
tty_set_ldisc() and tty_ldisc_hangup(), the ldisc_mutex does **not**
(and should not) play a role in acquiring or releasing ldisc references.
The only thing that needs to happen here
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/asm/thread_info.h | 155
arch/metag/kernel/process.c | 453 ++
2 files changed, 608 insertions(+), 0 deletions(-)
create mode 100644
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/asm/module.h | 37 +
arch/metag/kernel/module.c | 284 +++
2 files changed, 321 insertions(+), 0 deletions(-)
create mode 100644 arch/metag/include/asm/module.h
create mode
Add metag system call and gateway page interfaces. The metag
architecture port uses the generic system call numbers from
asm-generic/unistd.h, as well as a user gateway page mapped at
0x6000 which contains fast atomic primitives (depending on SMP) and
a fast method of accessing TLS data.
Add core IRQ handling for metag. The code in irq.c exposes the TBX
signal numbers as Linux IRQs.
Meta core internal interrupts (from HWSTATMETA and friends) are vectored
onto the TR1 core trigger for the current thread. This is demultiplexed
in irq_internal.c to individual Linux IRQs for each
Add trap code for metag. At the lowest level Meta traps (and return from
interrupt instruction - RTI) simply swap the PC and PCX registers and
optionally toggle the interrupt status bit (ISTAT). Low level TBX code
in tbipcx.S handles the core context save, determine the TBX signal
number based on
Here it is, you're initializing 'prefix' here although it is being
used in the previous patch. You should concentrate the whole prefix
initialization and passing in one patch so that there are no breakages.
Yes I probably could have broken up the patches in a cleaner way. Thanks.
Also,
Add signal handling code for metag.
Signed-off-by: James Hogan james.ho...@imgtec.com
---
arch/metag/include/uapi/asm/sigcontext.h | 31 +++
arch/metag/include/uapi/asm/siginfo.h|8 +
arch/metag/kernel/signal.c | 345 ++
3 files changed, 384
101 - 200 of 1044 matches
Mail list logo
