This patch adds maintainer for maxim audio codecs.
Signed-off-by: Anish Kumar
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8bdd7a7..2128586 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7387,6 +7387,13 @@ S: Supported
F
This patch adds maintainer for maxim audio codecs.
Signed-off-by: Anish Kumar yesanishh...@gmail.com
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8bdd7a7..2128586 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7387,6 +7387,13 @@ S
small values).
As suggested by Wim Van Sebroeck & Guenter Roeck we should
add this functionality of individual watchdog drivers in the core
watchdog core.
Signed-off-by: anish kumar
---
drivers/watchdog/watchdog_dev.c | 34 +-
include/linux/watchd
small values).
As suggested by Wim Van Sebroeck Guenter Roeck we should
add this functionality of individual watchdog drivers in the core
watchdog core.
Signed-off-by: anish kumar anish198519851...@gmail.com
---
drivers/watchdog/watchdog_dev.c | 34 +-
include
Commit-ID: b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Gitweb: http://git.kernel.org/tip/b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Author: anish kumar
AuthorDate: Tue, 12 Mar 2013 14:44:08 -0400
Committer: Ingo Molnar
CommitDate: Thu, 14 Mar 2013 08:24:05 +0100
watchdog: Add comments
Commit-ID: b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Gitweb: http://git.kernel.org/tip/b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Author: anish kumar anish198519851...@gmail.com
AuthorDate: Tue, 12 Mar 2013 14:44:08 -0400
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Thu, 14 Mar 2013
it will translate to always
if(true) so let's remove those checks as well(patch will be sent
later for that).
Is this return value for some future usecase(?), if yes then my
apologies.
Signed-off-by: anish kumar
---
include/linux/clocksource.h |6 +++---
kernel/time/clocksource.c |7
it will translate to always
if(true) so let's remove those checks as well(patch will be sent
later for that).
Is this return value for some future usecase(?), if yes then my
apologies.
Signed-off-by: anish kumar anish198519851...@gmail.com
---
include/linux/clocksource.h |6 +++---
kernel/time
on is being called use
dump_stack().This will give you the call chain leading up to your
function call which you are interested in.
>
>
>
> On Tue, Feb 19, 2013 at 9:25 PM, anish kumar
> wrote:
> > On Tue, 2013-02-19 at 12:16 +0530, chetan cr123 wrote:
> >> HI Al
On Tue, 2013-02-19 at 12:16 +0530, chetan cr123 wrote:
> HI All,
>
> I am working on Sd Card/Block driver
>
> I am registering it as both
>
> 1. register_blkdev()- BLOCK Regsiter
> 2. mmc_register_driver -- MMC regsiter
>
> and filling the mmc_driver structure.
>
> I am not
On Tue, 2013-02-19 at 12:16 +0530, chetan cr123 wrote:
HI All,
I am working on Sd Card/Block driver
I am registering it as both
1. register_blkdev()- BLOCK Regsiter
2. mmc_register_driver -- MMC regsiter
and filling the mmc_driver structure.
I am not able to see
function call which you are interested in.
On Tue, Feb 19, 2013 at 9:25 PM, anish kumar
anish198519851...@gmail.com wrote:
On Tue, 2013-02-19 at 12:16 +0530, chetan cr123 wrote:
HI All,
I am working on Sd Card/Block driver
I am registering it as both
1. register_blkdev
On Sun, 2013-02-17 at 14:37 +, Jonathan Andrews wrote:
> > > The dim pixel code is timing critical (but as I said only a tiny
> > > fraction of the total CPU usage). What I need to do is grab the CPU and
> > > prevent any context switch (IRQ or PREEMPT) for this period.
> > why you want to do
On Sun, 2013-02-17 at 14:37 +, Jonathan Andrews wrote:
The dim pixel code is timing critical (but as I said only a tiny
fraction of the total CPU usage). What I need to do is grab the CPU and
prevent any context switch (IRQ or PREEMPT) for this period.
why you want to do this?
On Sat, 2013-02-16 at 14:37 +, Jonathan Andrews wrote:
> I hope this is the correct place, I expect to get abused.
>
> I'm trying to do a mostly soft real-time task with a very small hard
> real time element.
>
> I've written some code to drive matrix LED signs using a Raspberry Pi.
>
>
From: anish kumar
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog->
On Sat, 2013-02-16 at 09:42 +0100, Ingo Molnar wrote:
> * Don Zickus wrote:
>
> > > >> > + /*
> > > >> > +* We shouldn't enable watchdog threads if it is
> > > >> > +* disabled.This is done by watchdog_disabled
> > > >> > +* variable check in watchdog_*_all_cpus
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog
On Sat, 2013-02-16 at 14:37 +, Jonathan Andrews wrote:
I hope this is the correct place, I expect to get abused.
I'm trying to do a mostly soft real-time task with a very small hard
real time element.
I've written some code to drive matrix LED signs using a Raspberry Pi.
Source
On Thu, 2013-02-14 at 16:33 +, Grant Likely wrote:
> On Thu, 14 Feb 2013 08:57:17 +0530, anish singh
> wrote:
> > On Thu, Feb 14, 2013 at 3:06 AM, Grant Likely
> > wrote:
> > > static int deferred_probe_initcall(void)
> > > {
> > > deferred_wq =
On Thu, 2013-02-14 at 16:33 +, Grant Likely wrote:
On Thu, 14 Feb 2013 08:57:17 +0530, anish singh anish198519851...@gmail.com
wrote:
On Thu, Feb 14, 2013 at 3:06 AM, Grant Likely grant.lik...@secretlab.ca
wrote:
static int deferred_probe_initcall(void)
{
deferred_wq
On Tue, 2013-02-12 at 10:58 +0800, Haojian Zhuang wrote:
> do_initcalls() could call all driver initialization code in kernel_init
> thread. It means that probe() function will be also called from that
> time. After this, kernel could access console & release __init section
> in the same thread.
>
On Tue, 2013-02-12 at 10:58 +0800, Haojian Zhuang wrote:
do_initcalls() could call all driver initialization code in kernel_init
thread. It means that probe() function will be also called from that
time. After this, kernel could access console release __init section
in the same thread.
But
On Sat, 2013-02-09 at 14:57 +0800, Peter Teoh wrote:
>
>
> On Sat, Feb 9, 2013 at 1:47 PM, anish kumar
> .
> Timer interrupts is supposed to cause scheduling and scheduler
> may or
> may not pick up your last process(we always use the
On Sat, 2013-02-09 at 14:57 +0800, Peter Teoh wrote:
On Sat, Feb 9, 2013 at 1:47 PM, anish kumar
.
Timer interrupts is supposed to cause scheduling and scheduler
may or
may not pick up your last process(we always use the term
task in
kernel space
On Tue, 2013-02-05 at 16:18 -0500, valdis.kletni...@vt.edu wrote:
> On Wed, 06 Feb 2013 04:43:20 +0800, Jimmy Pan said:
>
> > in fact, i've been always wondering what is the relationship between dmesg
> > and /var/log/message. they diverse a lot...
dmesg is provided by kernel using cat
On Tue, 2013-02-05 at 16:18 -0500, valdis.kletni...@vt.edu wrote:
On Wed, 06 Feb 2013 04:43:20 +0800, Jimmy Pan said:
in fact, i've been always wondering what is the relationship between dmesg
and /var/log/message. they diverse a lot...
dmesg is provided by kernel using cat /proc/kmsg.
Commit-ID: c02cf5f8ed6137e2b3b2f10e0fca336e06e09ba4
Gitweb: http://git.kernel.org/tip/c02cf5f8ed6137e2b3b2f10e0fca336e06e09ba4
Author: anish kumar
AuthorDate: Sun, 3 Feb 2013 22:08:23 +0100
Committer: Ingo Molnar
CommitDate: Mon, 4 Feb 2013 11:50:59 +0100
irq_work: Remove return value
Commit-ID: c02cf5f8ed6137e2b3b2f10e0fca336e06e09ba4
Gitweb: http://git.kernel.org/tip/c02cf5f8ed6137e2b3b2f10e0fca336e06e09ba4
Author: anish kumar anish198519851...@gmail.com
AuthorDate: Sun, 3 Feb 2013 22:08:23 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Mon, 4 Feb 2013 11
From: anish kumar
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog->
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog
On Fri, 2013-02-01 at 09:59 -0500, Don Zickus wrote:
> On Fri, Feb 01, 2013 at 07:19:07PM +0530, anish kumar wrote:
> > From: anish kumar
> >
> > This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
> > multifold.
> > Uses are:
> > 1.
On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
> 2012/11/3 anish kumar :
> > From: anish kumar
> >
> > As no one is using the return value of irq_work_queue function
> > it is better to just make it void.
> >
> > Acked-by: Steven
Please ignore this patch.
On Fri, 2013-02-01 at 19:03 +0530, anish kumar wrote:
> From: anish kumar
>
> This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
> multifold.
> Uses are:
> 1. Check if smpboot_register_percpu_thread function passed.
> 2.
From: anish kumar
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog->
From: anish kumar
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog->
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog
Please ignore this patch.
On Fri, 2013-02-01 at 19:03 +0530, anish kumar wrote:
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes
On Sat, 2013-01-26 at 17:24 +0100, Frederic Weisbecker wrote:
2012/11/3 anish kumar anish198519851...@gmail.com:
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt
On Fri, 2013-02-01 at 09:59 -0500, Don Zickus wrote:
On Fri, Feb 01, 2013 at 07:19:07PM +0530, anish kumar wrote:
From: anish kumar anish198519851...@gmail.com
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check
On Wed, 2013-01-30 at 10:51 -0500, Don Zickus wrote:
> On Tue, Jan 29, 2013 at 10:48:27PM +0530, anish kumar wrote:
> > Sorry for digressing from the topic but I think there is something wrong
> > with my understanding or something wrong with the code.So I guess Don
> > can c
On Wed, 2013-01-30 at 10:51 -0500, Don Zickus wrote:
On Tue, Jan 29, 2013 at 10:48:27PM +0530, anish kumar wrote:
Sorry for digressing from the topic but I think there is something wrong
with my understanding or something wrong with the code.So I guess Don
can clarify this.
If I pass
On Tue, 2013-01-29 at 10:33 -0500, Don Zickus wrote:
> Hi Mike,
>
> On Tue, Jan 29, 2013 at 05:42:43PM +0400, Mike Lykov wrote:
> >
> > So my questions:
> >
> > 1. Are there a BUG in soft lockup detection mechanizm? Changing
> > watchdog_thresh to 30 have a side effect in production - D-state
>
On Tue, 2013-01-29 at 10:33 -0500, Don Zickus wrote:
Hi Mike,
On Tue, Jan 29, 2013 at 05:42:43PM +0400, Mike Lykov wrote:
So my questions:
1. Are there a BUG in soft lockup detection mechanizm? Changing
watchdog_thresh to 30 have a side effect in production - D-state
userspace
From: anish kumar
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt
Signed-off-by: anish kumar
---
include/linux/irq_work.h |2 +-
kernel/irq_work.c|5 ++---
2 files changed, 3 insertions(+), 4 deletions
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt rost...@goodmis.org
Signed-off-by: anish kumar anish198519851...@gmail.com
---
include/linux/irq_work.h |2 +-
kernel
On Wed, 2013-01-16 at 10:25 +, Anuz Pratap Singh Tomar wrote:
>
>
> On Tue, Jan 15, 2013 at 6:31 AM, horseriver
> wrote:
> hi:
>
>what is the function of do_softirq()?
Softirq is basically same as bottom half except it is run in irq
context.So the question which
On Wed, 2013-01-16 at 10:25 +, Anuz Pratap Singh Tomar wrote:
On Tue, Jan 15, 2013 at 6:31 AM, horseriver horseriv...@gmail.com
wrote:
hi:
what is the function of do_softirq()?
Softirq is basically same as bottom half except it is run in irq
context.So the
>From your comments in this thread https://lkml.org/lkml/2011/3/25/723
>The msm watchdog driver is present in kernel only. It does not use the
>built-in Linux watchdog api. This is because the primary function of
>our watchdog is detecting bus lockups and interrupts being turned off
Doesn't
From your comments in this thread https://lkml.org/lkml/2011/3/25/723
The msm watchdog driver is present in kernel only. It does not use the
built-in Linux watchdog api. This is because the primary function of
our watchdog is detecting bus lockups and interrupts being turned off
Doesn't linux
On Sat, 2012-12-22 at 23:11 +0800, Woody Wu wrote:
> On Fri, Dec 21, 2012 at 01:33:03PM -0800, anish kumar wrote:
> > On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
> > > On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
> > > > On Dec 20, 2
On Mon, 2012-12-24 at 22:10 +0800, Woody Wu wrote:
> On Fri, Dec 21, 2012 at 01:33:03PM -0800, anish kumar wrote:
> > On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
> > > On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
> > > > On Dec 20, 2
On Mon, 2012-12-24 at 22:10 +0800, Woody Wu wrote:
On Fri, Dec 21, 2012 at 01:33:03PM -0800, anish kumar wrote:
On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
On Dec 20, 2012 6:30 AM, Woody Wu narkewo...@gmail.com wrote
On Sat, 2012-12-22 at 23:11 +0800, Woody Wu wrote:
On Fri, Dec 21, 2012 at 01:33:03PM -0800, anish kumar wrote:
On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
On Dec 20, 2012 6:30 AM, Woody Wu narkewo...@gmail.com wrote
On Thu, 2012-12-27 at 11:22 -0500, jonsm...@gmail.com wrote:
> On Thu, Dec 27, 2012 at 3:27 AM, Woody Wu wrote:
> > Hi, list
> >
> > I know this might be a very basic question. But I really don't clear at
> > it.
> >
> > Can a peripheral chip that claims to be ISA or PCI device be used in a
> >
On Thu, 2012-12-27 at 10:51 +0100, Geert Uytterhoeven wrote:
> On Thu, Dec 27, 2012 at 9:27 AM, Woody Wu wrote:
> > Can a peripheral chip that claims to be ISA or PCI device be used in a
> > ARM based embedded system? For these kind of chips, I only concern
> > about the planar kind of devices,
On Thu, 2012-12-27 at 10:51 +0100, Geert Uytterhoeven wrote:
On Thu, Dec 27, 2012 at 9:27 AM, Woody Wu narkewo...@gmail.com wrote:
Can a peripheral chip that claims to be ISA or PCI device be used in a
ARM based embedded system? For these kind of chips, I only concern
about the planar kind
On Thu, 2012-12-27 at 11:22 -0500, jonsm...@gmail.com wrote:
On Thu, Dec 27, 2012 at 3:27 AM, Woody Wu narkewo...@gmail.com wrote:
Hi, list
I know this might be a very basic question. But I really don't clear at
it.
Can a peripheral chip that claims to be ISA or PCI device be used in
On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
> On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
> > On Dec 20, 2012 6:30 AM, "Woody Wu" wrote:
> > >
> > > Hi, List
> > >
> > > Where is the Kernel code that handles external interrupts? I want to
> > > have a look at it but
On Fri, 2012-12-21 at 23:34 +0800, Woody Wu wrote:
On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
On Dec 20, 2012 6:30 AM, Woody Wu narkewo...@gmail.com wrote:
Hi, List
Where is the Kernel code that handles external interrupts? I want to
have a look at it but
On Fri, 2012-12-14 at 18:05 +1100, NeilBrown wrote:
> On Mon, 10 Sep 2012 10:57:07 -0700 Kevin Hilman
> wrote:
>
>
> > OK thanks, I'll queue this up for v3.6-rc as this should qualify as a
> > regression.
>
> I don't think this did actually get queued. At least I'm still seeing the
> bug in
On Fri, 2012-12-14 at 18:05 +1100, NeilBrown wrote:
On Mon, 10 Sep 2012 10:57:07 -0700 Kevin Hilman khil...@deeprootsystems.com
wrote:
OK thanks, I'll queue this up for v3.6-rc as this should qualify as a
regression.
I don't think this did actually get queued. At least I'm still
On Sat, 2012-12-08 at 17:37 +0100, Julia Lawall wrote:
> The function pm860x_charger_probe in the file
> drivers/power/88pm860x_charger.c contains the following code:
>
> count = pdev->num_resources;
> for (i = 0, j = 0; i < count; i++) {
> info->irq[j] =
On Sat, 2012-12-08 at 17:37 +0100, Julia Lawall wrote:
The function pm860x_charger_probe in the file
drivers/power/88pm860x_charger.c contains the following code:
count = pdev-num_resources;
for (i = 0, j = 0; i count; i++) {
info-irq[j] =
On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
> > I could imagine declaring the activity request buttons to be "input", but
> > for
> > presence detects it is a bit far fetched and would add too much complexity.
>
> Android tries to address this with its switch class driver, but I'm not
>
On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
I could imagine declaring the activity request buttons to be input, but
for
presence detects it is a bit far fetched and would add too much complexity.
Android tries to address this with its switch class driver, but I'm not
sure its
On Fri, 2012-12-07 at 15:02 +0800, Han Pingtian wrote:
> Hi there,
>
> I'm wondering this is a typo in Documentation/kernel-parameters.txt
> about "kernelcore=":
>
> In the event, a node is too small to have both
> kernelcore and Movable pages, kernelcore pages will
> take
On Fri, 2012-12-07 at 15:02 +0800, Han Pingtian wrote:
Hi there,
I'm wondering this is a typo in Documentation/kernel-parameters.txt
about kernelcore=:
In the event, a node is too small to have both
kernelcore and Movable pages, kernelcore pages will
take priority
On Sat, 2012-12-01 at 19:05 +0100, Linus Walleij wrote:
> This updates the IRQdomain documentation a bit, by adding a more
> verbose explanation to why we need this, and by adding some
> extended documentation of the irq_domain_simple() usecase.
>
> Signed-off-by: Linus Walleij
Thanks for doing
On Sat, 2012-12-01 at 19:05 +0100, Linus Walleij wrote:
This updates the IRQdomain documentation a bit, by adding a more
verbose explanation to why we need this, and by adding some
extended documentation of the irq_domain_simple() usecase.
Signed-off-by: Linus Walleij
On Mon, 2012-12-03 at 01:53 +, Tc, Jenny wrote:
> > We discussed about this patch and then suggest some method to resolve this
> > issue by Myungjoo Ham. Why don't you write additional feature or your
> > opinion based on following patch by Myungjoo Ham?
> > -
> >
On Mon, 2012-12-03 at 01:53 +, Tc, Jenny wrote:
We discussed about this patch and then suggest some method to resolve this
issue by Myungjoo Ham. Why don't you write additional feature or your
opinion based on following patch by Myungjoo Ham?
-
On Wed, 2012-11-28 at 20:10 +0530, manty kuma wrote:
> In linux interrupt programming, we do request_irq(...) in this
> function, the first argument is irq number. If i am not wrong, this is
> the interrupt line that we are requesting from kernel. For one
Right.
> particular hardware, is this IRQ
On Wed, 2012-11-28 at 20:10 +0530, manty kuma wrote:
In linux interrupt programming, we do request_irq(...) in this
function, the first argument is irq number. If i am not wrong, this is
the interrupt line that we are requesting from kernel. For one
Right.
particular hardware, is this IRQ
On Fri, 2012-11-09 at 14:05 +, Tc, Jenny wrote:
> > I think that the role of extcon subsystem notify changed
> > state(attached/detached) of cable to notifiee, but if you want to add
> > property feature of cable, you should solve ambiguous issues.
> >
> > First,
> > This patch only support
On Fri, 2012-11-09 at 14:05 +, Tc, Jenny wrote:
I think that the role of extcon subsystem notify changed
state(attached/detached) of cable to notifiee, but if you want to add
property feature of cable, you should solve ambiguous issues.
First,
This patch only support the
On Wed, 2012-11-07 at 17:45 +0100, Nicholas Mc Guire wrote:
> On Wed, 07 Nov 2012, Hendrik Visage wrote:
>
> > On Thu, Nov 8, 2012 at 9:01 AM, Jimmy Pan wrote:
> > > I understand how atomic operation work on unary core processors, I think
> > > it just disables the interrupt and dominate the
On Wed, 2012-11-07 at 17:45 +0100, Nicholas Mc Guire wrote:
On Wed, 07 Nov 2012, Hendrik Visage wrote:
On Thu, Nov 8, 2012 at 9:01 AM, Jimmy Pan dsp...@gmail.com wrote:
I understand how atomic operation work on unary core processors, I think
it just disables the interrupt and dominate
Hello,
I have below question and I would really appreciate a _CORRECT_ answer.
What are the sequence of steps that happen in CPU, cache, TLB, VM, HDD
leading to execution of “x = 7” which isn’t present in cache or sysmem
nor translation in TLB. Also specify if any interrupts, exceptions or
Hello Dan,
Is this patch of yours picked up by anyone?
On Sun, 2012-09-30 at 09:38 +0530, anish kumar wrote:
> On Sat, 2012-09-29 at 10:13 +0300, Dan Carpenter wrote:
> > psy->properties is an enum (32 bit type) so adding sizeof() puts us
> > four times further along than we in
Hello Dan,
Is this patch of yours picked up by anyone?
On Sun, 2012-09-30 at 09:38 +0530, anish kumar wrote:
On Sat, 2012-09-29 at 10:13 +0300, Dan Carpenter wrote:
psy-properties is an enum (32 bit type) so adding sizeof() puts us
four times further along than we intended. It should
Hello,
I have below question and I would really appreciate a _CORRECT_ answer.
What are the sequence of steps that happen in CPU, cache, TLB, VM, HDD
leading to execution of “x = 7” which isn’t present in cache or sysmem
nor translation in TLB. Also specify if any interrupts, exceptions or
From: anish kumar
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt
Signed-off-by: anish kumar
---
kernel/irq_work.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/irq_work.c b
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt rost...@goodmis.org
Signed-off-by: anish kumar anish198519851...@gmail.com
---
kernel/irq_work.c |5 ++---
1 files changed
From: anish kumar
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Signed-off-by: anish kumar
---
kernel/irq_work.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/irq_work.c b/kernel/irq_work.c
index 1588e3b
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Signed-off-by: anish kumar anish198519851...@gmail.com
---
kernel/irq_work.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On Wed, 2012-10-31 at 10:15 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-31 at 23:02 +0900, anish kumar wrote:
> > From: anish kumar
> >
> > As no one is using the return value of irq_work_queue function
> > it is better to just make it void.
> >
> >
From: anish kumar
As no one is using the return value of irq_work_queue function
it is better to just make it void.
This patch is just a way to understand if there is some future
plan to use it but in any case please let me know the reason.
---
kernel/irq_work.c | 21 ++---
1
On Tue, 2012-10-30 at 14:45 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-31 at 03:33 +0900, anish kumar wrote:
>
> > > CPU 0 CPU 1
> > >
> > > data = something flags = IRQ_WORK_BUSY
> > > s
On Tue, 2012-10-30 at 22:23 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-31 at 01:36 +0100, Frederic Weisbecker wrote:
> > 2012/10/30 anish kumar :
> > > As I understand without the memory barrier proposed by you the situation
> > > wou
On Tue, 2012-10-30 at 22:23 -0400, Steven Rostedt wrote:
On Wed, 2012-10-31 at 01:36 +0100, Frederic Weisbecker wrote:
2012/10/30 anish kumar anish198519851...@gmail.com:
As I understand without the memory barrier proposed by you the situation
would be as below:
CPU 0
On Tue, 2012-10-30 at 14:45 -0400, Steven Rostedt wrote:
On Wed, 2012-10-31 at 03:33 +0900, anish kumar wrote:
CPU 0 CPU 1
data = something flags = IRQ_WORK_BUSY
smp_mb() (implicit with cmpxchg smp_mb()
on flags
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
This patch is just a way to understand if there is some future
plan to use it but in any case please let me know the reason.
---
kernel/irq_work.c
On Wed, 2012-10-31 at 10:15 -0400, Steven Rostedt wrote:
On Wed, 2012-10-31 at 23:02 +0900, anish kumar wrote:
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
This patch is just a way
> The IRQ_WORK_BUSY flag is set right before we execute the
> work. Once this flag value is set, the work enters a
> claimable state again.
>
> This is necessary because if we want to enqueue a work but we
> fail the claim, we want to ensure that the CPU where that work
> is still pending will
The IRQ_WORK_BUSY flag is set right before we execute the
work. Once this flag value is set, the work enters a
claimable state again.
This is necessary because if we want to enqueue a work but we
fail the claim, we want to ensure that the CPU where that work
is still pending will see and
On Sat, 2012-10-27 at 09:23 +0800, Ming Lei wrote:
> This patch introduces one module parameter of 'path' in firmware_class
> to support customizing firmware image search path, so that people can
> use its own firmware path if the default built-in paths can't meet their
> demand[1], and the
On Sat, 2012-10-27 at 09:23 +0800, Ming Lei wrote:
This patch introduces one module parameter of 'path' in firmware_class
to support customizing firmware image search path, so that people can
use its own firmware path if the default built-in paths can't meet their
demand[1], and the typical
ping...
On Sat, 2012-10-13 at 00:32 +0900, anish kumar wrote:?
> Hello tglx,
>
> I just found the below inconsistency while going through the code.
>
>
> kernel/irq/manage.c
>
> if (new->flags & IRQF_ONESHOT) {
> /*
> * Th
1 - 100 of 223 matches
Mail list logo
