Hi Kieran,
On Friday 25 Nov 2016 18:40:34 Kieran Bingham wrote:
> On 25/11/16 17:10, Laurent Pinchart wrote:
> > On Friday 25 Nov 2016 13:59:16 Kieran Bingham wrote:
> >> From: Kieran Bingham
> >>
> >> Provide a test to verify the hardware completes a functional test whilst
> >> performing a sus
On 25/11/16 18:21, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Friday 25 Nov 2016 13:59:12 Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Provide a utility script to execute all vsp unit tests, as well
>> as the option to execute multiple iterations of the suite
Hi Laurent,
On 25/11/16 17:10, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Friday 25 Nov 2016 13:59:16 Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Provide a test to verify the hardware completes a functional test whilst
>> performing a suspend resume cycle i
Hi Kieran,
On Friday 25 Nov 2016 18:10:10 Kieran Bingham wrote:
> On 25/11/16 17:40, Laurent Pinchart wrote:
> > On Friday 25 Nov 2016 13:59:14 Kieran Bingham wrote:
> >> From: Kieran Bingham
> >>
> >> Extend the logger such that it will detect the tracing system, and also
> >> append print stat
Hi Kieran,
Thank you for the patch.
On Friday 25 Nov 2016 13:59:12 Kieran Bingham wrote:
> From: Kieran Bingham
>
> Provide a utility script to execute all vsp unit tests, as well
> as the option to execute multiple iterations of the suite.
>
> Signed-off-by: Kieran Bingham
> ---
> scripts/v
Hi Laurent,
On 25/11/16 17:40, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Friday 25 Nov 2016 13:59:14 Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Extend the logger such that it will detect the tracing system, and also
>> append print statement to this ring
On 25/11/16 17:13, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Friday 25 Nov 2016 13:59:15 Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Provide a test to verify the hardware is functional both before and
>> after entering a suspend / resume cycle. Make use o
Hi Laurent,
Thanks for the review :D
On 25/11/16 17:55, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Friday 25 Nov 2016 13:59:13 Kieran Bingham wrote:
>> From: Kieran Bingham
>>
>> Identify the size and format from the test output filename, and pass
>> to raw2rgbpnm
Hi Kieran,
Thank you for the patch.
On Friday 25 Nov 2016 13:59:13 Kieran Bingham wrote:
> From: Kieran Bingham
>
> Identify the size and format from the test output filename, and pass
> to raw2rgbpnm for conversion to a PNM file.
>
> From there we can convert easily to a PNG output file.
>
>
Hi Kieran,
Thank you for the patch.
On Friday 25 Nov 2016 13:59:14 Kieran Bingham wrote:
> From: Kieran Bingham
>
> Extend the logger such that it will detect the tracing system, and also
> append print statement to this ring buffer.
>
> This provides the relevant logging output interspersed i
Hi Kieran,
Thank you for the patch.
On Friday 25 Nov 2016 13:59:15 Kieran Bingham wrote:
> From: Kieran Bingham
>
> Provide a test to verify the hardware is functional both before and
> after entering a suspend / resume cycle. Make use of the
> /sys/power/pm_test functionality provided by CONFI
Hi Kieran,
Thank you for the patch.
On Friday 25 Nov 2016 13:59:16 Kieran Bingham wrote:
> From: Kieran Bingham
>
> Provide a test to verify the hardware completes a functional test whilst
> performing a suspend resume cycle in parallel. Make use of the
> /sys/power/pm_test functionality provid
Hello DT maintainers,
In one of the Renesas SoCs we have a device called DRIF (Digital Radio
Interface) controller. A DRIF channel contains 4 external pins - SCK, SYNC,
Data pins D0 & D1.
Internally a DRIF channel is made up of two SPI slave devices (also called
sub-channels here) that share
From: Kieran Bingham
Extend the logger such that it will detect the tracing system, and also
append print statement to this ring buffer.
This provides the relevant logging output interspersed in the ftrace
logs for an effective solution to identifying the actions that caused
the traces to occur
From: Kieran Bingham
Provide a test to verify the hardware is functional both before and
after entering a suspend / resume cycle. Make use of the
/sys/power/pm_test functionality provided by CONFIG_PM_DEBUG to perform
the testing
Signed-off-by: Kieran Bingham
---
tests/vsp-unit-test-0019.sh |
From: Kieran Bingham
Identify the size and format from the test output filename, and pass
to raw2rgbpnm for conversion to a PNM file.
>From there we can convert easily to a PNG output file.
Signed-off-by: Kieran Bingham
---
scripts/Makefile | 2 +-
scripts/bin2png.sh | 34 +
From: Kieran Bingham
Provide a utility script to execute all vsp unit tests, as well
as the option to execute multiple iterations of the suite.
Signed-off-by: Kieran Bingham
---
scripts/vsp-tests.sh | 46 ++
1 file changed, 46 insertions(+)
create m
From: Kieran Bingham
Provide a test to verify the hardware completes a functional test whilst
performing a suspend resume cycle in parallel. Make use of the
/sys/power/pm_test functionality provided by CONFIG_PM_DEBUG to perform
the testing
Signed-off-by: Kieran Bingham
---
tests/vsp-unit-test
From: Kieran Bingham
Provide two tests for suspend/resume cycles. One will verify the VSP1 is
functional with a test before and after a suspend cycle. The other will
maintain an active pipeline which must succeed despite a suspend resume cycle
occuring in the middle of the test.
Along side these
Hi Shailendra,
Thank you for the patch.
The subject line is missing something (and has an extra -), I would phrase it
as
"v4l: vsp1: Clean up file handle in open() error path"
(Mauro's scripts will add the "[media]" prefix when applying, so there's no
need to add it manually)
The same commen
On 24 November 2016 at 11:48, Simon Horman wrote:
> Remove documentation of support for the SH7372 (SH-Mobile AP4) from the MMC
> driver. The driver itself appears to have no SH7372 specific code.
>
> Commit edf4100906044225 ("ARM: shmobile: sh7372 dtsi: Remove Legacy file")
> removes this SoC fro
On 25 November 2016 at 08:56, Simon Horman wrote:
> Simply document new compatibility strings as the driver is already
> activated using a fallback compatibility string.
>
> These compat strings are in keeping with those for all other
> Renesas ARM based SoCs with sh_mmcif enabled in mainline.
>
>
On Fri, Nov 25, 2016 at 11:15:45AM +0100, Geert Uytterhoeven wrote:
> Already in use for "oki,ml86v7667".
>
> Signed-off-by: Geert Uytterhoeven
Reviewed-by: Simon Horman
Hi Geert-san,
> From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com] On
> Behalf Of Geert Uytterhoeven
> Sent: Friday, November 25, 2016 4:54 PM
>
> Hi Shimoda-san,
>
> On Fri, Nov 25, 2016 at 7:55 AM, Yoshihiro Shimoda
> wrote:
> >> As we're getting close to the opening of
On Thu, Nov 24, 2016 at 9:15 PM, Simon Horman
wrote:
> Use the SoC-specific compat string for mmcif in DT for the r8a73a4 SoC.
> This is in keeping with the use of compat strings for mmcif for other
> Renesas ARM based SoCs.
>
> Signed-off-by: Simon Horman
Acked-by: Geert Uytterhoeven
Gr{oetje
Already in use for "oki,ml86v7667".
Signed-off-by: Geert Uytterhoeven
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index
On Fri, Nov 25, 2016 at 8:56 AM, Simon Horman
wrote:
> Simply document new compatibility strings as the driver is already
> activated using a fallback compatibility string.
>
> These compat strings are in keeping with those for all other
> Renesas ARM based SoCs with sh_mmcif enabled in mainline.
Hi Magnus,
(this time with CC kept)
On Fri, Nov 25, 2016 at 9:16 AM, Magnus Damm wrote:
> On Mon, Nov 21, 2016 at 8:09 PM, Geert Uytterhoeven
> wrote:
>> On Thu, Nov 17, 2016 at 9:51 AM, Magnus Damm wrote:
>>> On Thu, Nov 17, 2016 at 5:31 PM, Geert Uytterhoeven
>>> wrote:
On Thu, Nov 17,
On Thu, Nov 24, 2016 at 9:15 PM, Simon Horman
wrote:
> Use the SoC-specific compat string for mmcif in DT for the r8a7778 SoC.
> This is in keeping with the use of compat strings for mmcif for other
> Renesas ARM based SoCs.
>
> Signed-off-by: Simon Horman
Acked-by: Geert Uytterhoeven
Gr{oetje
Hi Geert,
On Fri, Nov 25, 2016 at 6:00 PM, Geert Uytterhoeven
wrote:
> On Mon, Oct 31, 2016 at 6:08 PM, Geert Uytterhoeven
> wrote:
>> By default, the DMA mask covers only the low 32-bit address space, which
>> causes SWIOTLB on arm64 to fall back to a bounce buffer for DMA
>> transfers involvin
Hi Geert,
On Mon, Nov 21, 2016 at 8:09 PM, Geert Uytterhoeven
wrote:
> Hi Magnus,
>
> On Thu, Nov 17, 2016 at 9:51 AM, Magnus Damm wrote:
>> On Thu, Nov 17, 2016 at 5:31 PM, Geert Uytterhoeven
>> wrote:
>>> On Thu, Nov 17, 2016 at 3:28 AM, Magnus Damm wrote:
First of all, we might have sl
On Thu, Nov 24, 2016 at 9:15 PM, Simon Horman
wrote:
> Use the SoC-specific compat string for mmcif in DT for the sh73a0 SoC.
> This is in keeping with the use of compat strings for mmcif for other
> Renesas ARM based SoCs.
>
> Signed-off-by: Simon Horman
Acked-by: Geert Uytterhoeven
Gr{oetje,
On Mon, Oct 31, 2016 at 6:08 PM, Geert Uytterhoeven
wrote:
> By default, the DMA mask covers only the low 32-bit address space, which
> causes SWIOTLB on arm64 to fall back to a bounce buffer for DMA
> transfers involving memory outside the 32-bit address space.
>
> The R-Car DMA controller hardwa
Hi Ulrich,
On Thu, Nov 17, 2016 at 6:27 PM, Ulrich Hecht wrote:
> On Thu, Nov 17, 2016 at 6:05 AM, Magnus Damm wrote:
>> Thanks for your efforts! Quick question, the dependency on zlib seems
>> to come from using adler32() for checksum comparison. In the code you
>> seem to compare the total amo
34 matches
Mail list logo
