Hi Sangwook,
On 09/05/2012 02:28 PM, Sangwook Lee wrote:
> This patch adds driver for S5K4ECGX sensor with embedded ISP SoC,
> S5K4ECGX, which is a 5M CMOS Image sensor from Samsung
> The driver implements preview mode of the S5K4ECGX sensor.
> capture (snapshot) operation, face detection are miss
On 9/5/2012 10:45 AM, Rajagopal Venkat wrote:
> On 5 September 2012 22:52, Arjan van de Ven wrote:
>> On 9/5/2012 10:19 AM, Rajagopal Venkat wrote:
>>> On 5 September 2012 22:39, Arjan van de Ven wrote:
On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
>> measure1:
>> ev3.start
>> ev1
On 5 September 2012 22:52, Arjan van de Ven wrote:
> On 9/5/2012 10:19 AM, Rajagopal Venkat wrote:
>> On 5 September 2012 22:39, Arjan van de Ven wrote:
>>> On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
> measure1:
> ev3.start
> ev1.end <
evX.end <
These events
On 9/5/2012 10:19 AM, Rajagopal Venkat wrote:
> On 5 September 2012 22:39, Arjan van de Ven wrote:
>> On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
measure1:
ev3.start
ev1.end <
>>>
>>> evX.end <
>>> These events are causing numbers to go wrong.
>>
>> but out of a 20 second
On 5 September 2012 22:39, Arjan van de Ven wrote:
> On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
>>> measure1:
>>> ev3.start
>>> ev1.end <
>>
>> evX.end <
>> These events are causing numbers to go wrong.
>
> but out of a 20 second window.. this is a tiny tiny window...
> if you see 100.
On 9/5/2012 9:56 AM, Rajagopal Venkat wrote:
>> measure1:
>> ev3.start
>> ev1.end <
>
> evX.end <
> These events are causing numbers to go wrong.
but out of a 20 second window.. this is a tiny tiny window...
if you see 100.1% I'd buy this reasoning.
but you're seeing much more than that
On 5 September 2012 18:14, Sergey Senozhatsky
wrote:
> Hi,
>
> On (09/05/12 15:52), Rajagopal Venkat wrote:
>> Incorrect timer and work perf events timestamp tracing is one
>> of the reason for reporting usage over 100%. This patch will
>> resolve the issue by
>> - rejecting the events for which e
On 5 September 2012 19:16, Morten Rasmussen wrote:
> The patch is already in the original patch set, so I'm not sure why it
> is missing.
>
> http://linux-arm.org/git?p=arm-bls.git;a=commit;h=1416200dd62551aa9ac4aa207b0c66651ccbff2c
>
> It needs to be there for the HMP scheduling to work.
Surpris
The bootwrapper is really doubling as firmware, so it doesn't make
sense for it to drop out of the Secure World before getting a
chance to parse its parameters and configuration.
Instead, it should make sense to delay switching to the Normal
World for as long as possible so that we have a chance t
Signed-off-by: Dave Martin
---
boot.S| 15 +--
semi_loader.h |6 --
2 files changed, 17 insertions(+), 4 deletions(-)
diff --git a/boot.S b/boot.S
index 128f74e..8ab68ba 100644
--- a/boot.S
+++ b/boot.S
@@ -96,8 +96,6 @@ start:
mov r7, #0xfff0
* Split Hyp mode entry out into a separate macro.
* hvc now jumps back to the caller in Hyp mode instead of
branching to a fixed label.
Signed-off-by: Dave Martin
---
boot.S | 23 +++
1 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/boot.S b/boot.S
in
Currently, it looks like we rely on luck in order to fall through
to the correct vector when a Hyp Trap exception occurs.
This patch aligns the Hyp mode vector table explicitly to a 32-byte
boundary, as required by the architecture.
Signed-off-by: Dave Martin
---
boot.S | 24 -
On Saturday, September 01, 2012, Rafael J. Wysocki wrote:
> On Friday, August 31, 2012, Daniel Lezcano wrote:
> > On 07/24/2012 11:06 PM, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Jul 24, 2012 at 11:12:29PM +0200, Daniel Lezcano wrote:
> > >> Remove the power field as it is not used.
> > >>
> > >>
On 09/05/2012 05:44 AM, Sergey Senozhatsky wrote:
Hi,
On (09/05/12 15:52), Rajagopal Venkat wrote:
Incorrect timer and work perf events timestamp tracing is one
of the reason for reporting usage over 100%. This patch will
resolve the issue by
- rejecting the events for which entry timestamp is
Hi Viresh,
On Mon, Sep 03, 2012 at 06:21:26AM +0100, Viresh Kumar wrote:
> On 28 August 2012 10:37, Viresh Kumar wrote:
> > I have updated
> >
> > https://wiki.linaro.org/WorkingGroups/PowerManagement/Process/bigLittleMPTree
> >
> > as per our last discussion. Please see if i have missed somethin
Hi,
On (09/05/12 15:52), Rajagopal Venkat wrote:
> Incorrect timer and work perf events timestamp tracing is one
> of the reason for reporting usage over 100%. This patch will
> resolve the issue by
> - rejecting the events for which entry timestamp is not recorded.
how is that possible?
do you m
This patch adds driver for S5K4ECGX sensor with embedded ISP SoC,
S5K4ECGX, which is a 5M CMOS Image sensor from Samsung
The driver implements preview mode of the S5K4ECGX sensor.
capture (snapshot) operation, face detection are missing now.
Following controls are supported:
contrast/saturation/bri
On Wed, Sep 5, 2012 at 3:52 PM, Rajagopal Venkat
wrote:
> Incorrect timer and work perf events timestamp tracing is one
> of the reason for reporting usage over 100%. This patch will
> resolve the issue by
> - rejecting the events for which entry timestamp is not recorded.
> Currently these events
On 09/05/12 17:19, the mail apparently from Andy Green included:
On 09/04/12 12:13, the mail apparently from Ricardo Salveti included:
Hi -
1) Can we have linux stable point release content in tilt-3.4?
Rather than
my doing it, isn't it better to add it to llc-3.4 and merge it on the lt
histor
Incorrect timer and work perf events timestamp tracing is one
of the reason for reporting usage over 100%. This patch will
resolve the issue by
- rejecting the events for which entry timestamp is not recorded.
Currently these events exit timestamp itself is considered as
usage period resulting in o
On 09/04/12 12:13, the mail apparently from Ricardo Salveti included:
Hi -
1) Can we have linux stable point release content in tilt-3.4? Rather than
my doing it, isn't it better to add it to llc-3.4 and merge it on the lt
history tree periodically? That way every lt can get them from one pla
21 matches
Mail list logo
