On July 22, 2016 12:18:48 AM GMT+08:00, John Stultz <john.stu...@linaro.org>
wrote:
>On Wed, Jul 20, 2016 at 11:27 PM, Andy Green <a...@warmcat.com> wrote:
>> On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz
><john.stu...@linaro.org> wrote:
>>>On
On July 22, 2016 12:18:48 AM GMT+08:00, John Stultz
wrote:
>On Wed, Jul 20, 2016 at 11:27 PM, Andy Green wrote:
>> On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz
> wrote:
>>>On Wed, Jul 20, 2016 at 9:26 PM, zhangfei
>>>wrote:
>>>>
>>&
On Thu, 2016-07-21 at 11:40 +0100, Mark Brown wrote:
> On Thu, Jul 21, 2016 at 02:27:02PM +0800, Andy Green wrote:
> >
> > On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz <john.stultz@lin
> > aro.org> wrote:
> > >
> > > On Wed, Jul 20, 2016 at 9:26
On Thu, 2016-07-21 at 11:40 +0100, Mark Brown wrote:
> On Thu, Jul 21, 2016 at 02:27:02PM +0800, Andy Green wrote:
> >
> > On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz > aro.org> wrote:
> > >
> > > On Wed, Jul 20, 2016 at 9:26 PM, zhangfei > >
On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz
wrote:
>On Wed, Jul 20, 2016 at 9:26 PM, zhangfei
>wrote:
>>
>>
>> On 07/21/2016 11:53 AM, John Stultz wrote:
>>>
>>> After lots of debugging on an occasional DMA ERR issue, I realized
>>> that
On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz
wrote:
>On Wed, Jul 20, 2016 at 9:26 PM, zhangfei
>wrote:
>>
>>
>> On 07/21/2016 11:53 AM, John Stultz wrote:
>>>
>>> After lots of debugging on an occasional DMA ERR issue, I realized
>>> that the desc structures which we point the dma
t;
> Cc: Vinod Koul <vinod.k...@intel.com>
> Cc: Dan Williams <dan.j.willi...@intel.com>
> Cc: Liam Girdwood <lgirdw...@gmail.com>
> Cc: Mark Brown <broo...@kernel.org>
> Cc: Jaroslav Kysela <pe...@perex.cz>
> Cc: Takashi Iwai <ti...@suse.com>
&
upstreaming it.
-Andy
> thanks
> -john
>
> Cc: Zhangfei Gao
> Cc: Jingoo Han
> Cc: Krzysztof Kozlowski
> Cc: Maxime Ripard
> Cc: Vinod Koul
> Cc: Dan Williams
> Cc: Liam Girdwood
> Cc: Mark Brown
> Cc: Jaroslav Kysela
> Cc: Takashi Iwai
> Cc: Wei X
Hi... looks good, just some small general comments.
On 15 December 2015 at 06:42, Joshua Henderson
wrote:
> From: Andrei Pistirica
>
> This driver supports the SDHCI host controller found on a PIC32.
>
> Signed-off-by: Andrei Pistirica
> Signed-off-by: Joshua Henderson
> Cc: Ralf Baechle
>
Hi... looks good, just some small general comments.
On 15 December 2015 at 06:42, Joshua Henderson
wrote:
> From: Andrei Pistirica
>
> This driver supports the SDHCI host controller found on a PIC32.
>
> Signed-off-by: Andrei
From: Andy Green
warning-elimination: android: binder
This commit in mainline (now) causes a couple of warnings
commit 975a1ac9a9fe65d66ee1726c0db6dc58e53d232a
Author: Arve Hjønnevåg
Date: Tue Oct 16 15:29:53 2012 -0700
Staging: android: binder: Add some tracepoints
This patch fixes
From: Andy Green andy.gr...@linaro.org
warning-elimination: android: binder
This commit in mainline (now) causes a couple of warnings
commit 975a1ac9a9fe65d66ee1726c0db6dc58e53d232a
Author: Arve Hjønnevåg a...@android.com
Date: Tue Oct 16 15:29:53 2012 -0700
Staging: android: binder: Add
On 26 June 2013 21:39, Prabhat Kumar Ravi wrote:
> Hi,
>
> On Wed, Jun 26, 2013 at 4:39 PM, Andy Green wrote:
>> Hi -
>>
>> Running perf test on 3.10-rc6 gives some unexpected behaviours.
>>
>> This is on a dual Cortex A9 board with perf userland cros
On 26 June 2013 21:39, Prabhat Kumar Ravi prabhatrav...@gmail.com wrote:
Hi,
On Wed, Jun 26, 2013 at 4:39 PM, Andy Green andy.gr...@linaro.org wrote:
Hi -
Running perf test on 3.10-rc6 gives some unexpected behaviours.
This is on a dual Cortex A9 board with perf userland cross-built from
Hi -
Running perf test on 3.10-rc6 gives some unexpected behaviours.
This is on a dual Cortex A9 board with perf userland cross-built from
same tree as the kernel.
root@aa9-eb:~# perf test
1: vmlinux symtab matches kallsyms: FAILED!
2: detect open syscall event
Hi -
Running perf test on 3.10-rc6 gives some unexpected behaviours.
This is on a dual Cortex A9 board with perf userland cross-built from
same tree as the kernel.
root@aa9-eb:~# perf test
1: vmlinux symtab matches kallsyms: FAILED!
2: detect open syscall event
this real scenario should be interesting to think about before
rejecting ^^
-Andy
--
Andy Green | Fujitsu Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/l
scenario should be interesting to think about before
rejecting ^^
-Andy
--
Andy Green | Fujitsu Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
to mediate,
Jassi is suggesting being able to do the client locking at your layer as
a primitive will simplify things, not least get rid of the mediation
driver. Your layer has concept of completion and notifier already so it
seems it wouldn't take much more.
-Andy
--
Andy Green | Fujitsu Landing
to mediate,
Jassi is suggesting being able to do the client locking at your layer as
a primitive will simplify things, not least get rid of the mediation
driver. Your layer has concept of completion and notifier already so it
seems it wouldn't take much more.
-Andy
--
Andy Green | Fujitsu Landing
of the PRCMU code
and on the multiplatform support for OMAP with mailbox enabled. We
can definitely collaborate on the improvements. Andy Green would also
be interested, as he is also looking into adopting the mailbox API.
To clarify Jassi works on my team, after I wrote two Mailbox drivers for
two
of the PRCMU code
and on the multiplatform support for OMAP with mailbox enabled. We
can definitely collaborate on the improvements. Andy Green would also
be interested, as he is also looking into adopting the mailbox API.
To clarify Jassi works on my team, after I wrote two Mailbox drivers for
two
esentation question
first, maybe there's a way forward defining the "power tree" in terms of
regulators, and then adding something in struct regulator that spams
readers with timestamped results if the regulator has a power monitoring
capability.
Then you can map the regulators in th
the regulators in the power tree to real devices by the
names or the supply stuff. Just a thought.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg
On 10/07/12 20:37, the mail apparently from Florian Fainelli included:
Hi -
Le jeudi 05 juillet 2012 04:44:33, Andy Green a écrit :
The following series adds some code to generate legal, locally administered
MAC addresses from OMAP4 CPU Die ID fuse data, and then adds a helper at
net/ethernet
On 10/07/12 20:37, the mail apparently from Florian Fainelli included:
Hi -
Le jeudi 05 juillet 2012 04:44:33, Andy Green a écrit :
The following series adds some code to generate legal, locally administered
MAC addresses from OMAP4 CPU Die ID fuse data, and then adds a helper at
net/ethernet
fault (esp as CONFIG_MODULE appeared in a quoted string).
Signed-off-by: Andy Green <[EMAIL PROTECTED]>
---
scripts/basic/fixdep.c |2 ++
1 file changed, 2 insertions(+)
Index: 2.6.21-1.3116.fc7-i686/scripts/basic/fixdep.c
===
--- 2
as CONFIG_MODULE appeared in a quoted string).
Signed-off-by: Andy Green [EMAIL PROTECTED]
---
scripts/basic/fixdep.c |2 ++
1 file changed, 2 insertions(+)
Index: 2.6.21-1.3116.fc7-i686/scripts/basic/fixdep.c
===
--- 2.6.21-1.3116.fc7-i686
28 matches
Mail list logo