Change the timer value to support at usecs range instead of
msecs. This allows to have different period sizes for a
given frequency.
Signed-off-by: Laxminath Kasam <lkasam@codeaurora.org>
ARCH_POPULATES_NODE_MAP is used by most of the other
architectures and allows finer-grained control of
how and where zones are placed.
Signed-off-by: Larry Bassel <lbassel@codeaurora.org>
Conflicts:
arch/arm/mm/init.c
Some RPM resources like RPM_CTL have configuration registers where
different bits mean different functionality. Add API to modify values
of bit values of RPM resources for active context.
Also, remove previously forced option to disallow-cpu-halt on RPM
from the driver.
Signed-off-by: Praveen Chidambaram <pchidamb@codeaurora.org>
This patch fixes following issues:
1. typecast unsigned int variable (irq) to integer
compare with zero.
2. Intializing baud variable
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
This patch fixes following issues:
1. Using snprintf instead of sprintf(deprecated api)
2. Typecast unsigned int variable (irq) to integer
to compare with zero.
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
-Add sysfs interface to read PM8921 HK/XOADC
and thermistor temperature measurements mapped
through MPP's.
-Move PM8921 ADC from directory /drivers/mfd to
/drivers/hwmon for userspace clients to read ADC
through hwmon.
CRs-Fixed: 302365
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
Conflicts:
drivers/mfd/Kconfig
The other masters in the MSM could be accessing the pmic while
pmic has raised the reset interrupt. This might cause pmic
lockups.
Disable the pmic arbiter by calling secure code when we handle
the reset interrupt from pmic. This will disable all the ssbi
transactions to the pmic avoiding a possible lockup.
Also since we wont be lowering ps_hold for pmic initiated startups
piggy back on lower_pshold to return from the power off function
so that we can call in the secure manager as the last step.
Additionally, since we will be busy looping until the pmic resets
us, pet the watchdog.
CRs-Fixed: 306410
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
In use cases with very high graphics for some time followed by
low constant usage, the power level is never dropped. Periodically
allow the TZ algorithm to run to see if any change in the external
conditions has occured.
CRs-fixed: 309131
Signed-off-by: Lucille Sylvester <lsylvest@codeaurora.org>
While logging to the kernel log, keep the last 20 or so messages in
a local buffer. This can be accessed by debugfs or through a crash
dump. This is useful when there is heavy logging to the kernel log
and sdio messages are lost.
Signed-off-by: Krishna Konda <kkonda@codeaurora.org>
Add these two interrupts managed by the wlan driver into the
msm_mpm_bypassed_apps_irqs list:
1. 234 = RIVA_APPS_WLAN_RX_DATA_AVAIL_IRQ
2. 235 = RIVA_APPS_WLAN_DATA_XFER_DONE_IRQ
Signed-off-by: David Collins <collinsd@codeaurora.org>
Even when CONFIG_MULTI_IRQ_HANDLER is selected, the core code
requires the arch_irq_handler_default macro to be defined as
a fallback.
It turns out nobody is using that particular feature as both PXA
and shmobile have all their machine descriptors populated with
the interrupt handler, leaving unused code (or empty macros) in
their entry-macro.S file just to be able to compile entry-armv.S.
Make CONFIG_MULTI_IRQ_HANDLER exclusive wrt arch_irq_handler_default,
which allows to remove one test from the hot path. Also cleanup both
PXA and shmobile entry-macro.S.
Cc: Eric Miao <eric.y.miao@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Taniya Das <tdas@codeaurora.org>
This avoids the irq entry assembly corrupting r5, thereby allowing it
to be preserved through to the svc exit code.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Taniya Das <tdas@codeaurora.org>
On Mon, Jul 11, 2011 at 3:52 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
...
> The __exception annotation on a function causes this to happen:
>
> [<c002406c>] (asm_do_IRQ+0x6c/0x8c) from [<c0024b84>]
> (__irq_svc+0x44/0xcc)
> Exception stack(0xc3897c78 to 0xc3897cc0)
> 7c60:
4022d320 4022e000
> 7c80: 08000075 00001000 c32273c0 c03ce1c0 c2b49b78 4022d000
c2b420b4 00000001
> 7ca0: 00000000 c3897cfc 00000000 c3897cc0 c00afc54 c002edd8
00000013 ffffffff
>
> Where that stack dump represents the pt_regs for the exception which
> happened. Any function found in while unwinding will cause this to
> be printed.
>
> If you insert a C function between the IRQ assembly and asm_do_IRQ,
> the
> dump you get from asm_do_IRQ will be the stack for your function,
> not
> the pt_regs. That makes the feature useless.
>
When __irq_svc - or any of the other exception handling assembly code -
calls the C code, the stack pointer will be pointing at the pt_regs
structure.
All the entry points into C code from the exception handling code are
marked with __exception or __exception_irq_enter to indicate that they
are one of the functions which has pt_regs above them.
Normally, when you've entered asm_do_IRQ() you will have this stack
layout (higher address towards top):
pt_regs
asm_do_IRQ frame
If you insert a C function between the exception assembly code and
asm_do_IRQ, you end up with this stack layout instead:
pt_regs
your function frame
asm_do_IRQ frame
This means when we unwind, we'll get to asm_do_IRQ, and rather than
dumping out the pt_regs, we'll dump out your functions stack frame
instead, because that's what is above the asm_do_IRQ stack frame
rather than the expected pt_regs structure.
The fix is to introduce handle_IRQ() for no exception stack dump, so
it can be called with MULTI_IRQ_HANDLER is selected and a C function
is between the assembly code and the actual IRQ handling code.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Eric Miao <eric.y.miao@gmail.com>
Signed-off-by: Taniya Das <tdas@codeaurora.org>
At both lcdc and dsi video mode panel, wait for vsync
interrupt instead of dmap_done interrupt to make sure a
single frame updated during every vsync period.
CRs-fixed: 305599
Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org>
This reverts commit 96fbbf3272449febc1a33861af1d275200563965.
NO_WAIT frame push need to be followed by a WAIT frame push so
that only a MDP kickoff necessary. Therefore this fix should be
done at user space program instead at driver.
Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org>
The current code relies on charge state changes to check battery charging
and notify bms. The charge state change interrupt can occur many times,
causing unnecessary checks on battery charging. Instead explicitly invoke
charging checks in case of events known to start/stop charging. On similar
lines disable the use of charge state change interrupts.
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Halt ispif immediately before stopping sensor streaming,
and start ispif before start sensor streaming.
Handle ispif reset properly using wait_for_completion*
instead of msleep().
Signed-off-by: Shuzhen Wang <shuzhenw@codeaurora.org>
Rename the module produced for the wcnss subsystem to reflect the fact
that it provides core services, and not just services for WLAN
Signed-off-by: Jeff Johnson <jjohnson@codeaurora.org>
Conflicts:
drivers/net/wireless/Makefile
The gain for EAR PA is not linear. So can not use TLV Mixer control
for setting gain. Only 6dB and 2dB gains are supported, since other
values for gain might cause performance issues.
Signed-off-by: Kiran Kandi <kkandi@codeaurora.org>
Store the link key persistently if one of the following is true:
1. this is a legacy link key
2. this is a changed combination key and there was a previously
stored one
3. neither local nor remote side had no-bonding as a requirement
4. the local side had dedicated bonding as a requirement
5. the remote side is using dedicated bonding since in that case
also the local requirements are set to dedicated bonding
If none of the above match only keep the link key around for
this connection and set the temporary flag for the device.
CRs-Fixed: 309161
Signed-off-by: Srinivas Krovvidi <skrovvid@codeaurora.org>
The function subsys_modem_crash_shutdown function will
be called from an atomic context via the panic notifier
chain. Make it safe to invoke in an atomic context.
Signed-off-by: Vikram Mulukutla <markivx@codeaurora.org>
FE/BE platform devices will be added to support ALSA
front-end and back-end in case WM8903 machine driver is
enabled.
Signed-off-by: Lei Zhou <leizhou@codeaurora.org>
Save and restore interrupt state when using spinlocks
to prevent re-enabling spinlocks when handling an
SMD notification.
CRs-Fixed: 303355
Signed-off-by: Eric Holmberg <eholmber@codeaurora.org>
This reverts commit a3f80de22b86c583f89f632259148e3ab42aaf20.
The bug that was causing this WARN has been fixed. Future
instances must be noted with the stack that caused the
condition; restore the WARN macro.
Signed-off-by: Vikram Mulukutla <markivx@codeaurora.org>
Instead of making other code dependent on #ifdef
CONFIG_MSM_SCM, add empty stubs for the scm functions
Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
This keeps track of the Session ID's used for voice and
sends them in the APR packet for SET & GET PARAMS
Signed-off-by: Ben Romberger <bromberg@codeaurora.org>
CRs-fixed: 308117
There was bug where we were not freeing the memory after event handling.
This patch adds the code to clear the skb memory.
Signed-off-by: Srinivasa Rao Uppala <uppalas@codeaurora.org>
