All of lore.kernel.org
 help / color / mirror / Atom feed
* [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N
@ 2019-06-17  0:35 Laurent Pinchart
  2019-06-17  8:29 ` Sergei Shtylyov
  2019-06-18 21:33 ` Kieran Bingham
  0 siblings, 2 replies; 4+ messages in thread
From: Laurent Pinchart @ 2019-06-17  0:35 UTC (permalink / raw)
  To: linux-renesas-soc; +Cc: Kieran Bingham

The BRU/BRS allocation test only covers the H3 ES2.0 SoC as that was the
only hardware platform supported by the DU driver that offered the
required features at the time the test was written. Now that M3-N is
supported in the DU driver, support it in the test script.

Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 tests/kms-test-brxalloc.py | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/tests/kms-test-brxalloc.py b/tests/kms-test-brxalloc.py
index 2e3f6cb8b39e..f1902f3baf1d 100755
--- a/tests/kms-test-brxalloc.py
+++ b/tests/kms-test-brxalloc.py
@@ -17,11 +17,10 @@ class BRxAllocTest(kmstest.KMSTest):
     def main(self):
         # This test requires usage of two CRTCs connected to the same VSPDL
         # instance to test dynamic assignment of the BRU and BRS to pipelines.
-        # This is only occurs on H3 ES2.0 (and M3N which we don't support yet).
-        # Check the SoC model through sysfs as we can't detected it through the
-        # DRM/KMS API.
+        # This is only occurs on H3 ES2.0 and M3N. Check the SoC model through
+        # sysfs as we can't detected it through the DRM/KMS API.
         soc = open("/sys/devices/soc0/soc_id", "rb").read().strip().decode()
-        if soc != "r8a7795":
+        if soc != "r8a7795" and soc != "r8a77965":
             self.skip("VSPDL (BRU+BRS) not available")
             return
 
-- 
Regards,

Laurent Pinchart


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N
  2019-06-17  0:35 [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N Laurent Pinchart
@ 2019-06-17  8:29 ` Sergei Shtylyov
  2019-06-17 20:26   ` Laurent Pinchart
  2019-06-18 21:33 ` Kieran Bingham
  1 sibling, 1 reply; 4+ messages in thread
From: Sergei Shtylyov @ 2019-06-17  8:29 UTC (permalink / raw)
  To: Laurent Pinchart, linux-renesas-soc; +Cc: Kieran Bingham

Hello!

On 17.06.2019 3:35, Laurent Pinchart wrote:

> The BRU/BRS allocation test only covers the H3 ES2.0 SoC as that was the
> only hardware platform supported by the DU driver that offered the
> required features at the time the test was written. Now that M3-N is
> supported in the DU driver, support it in the test script.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>   tests/kms-test-brxalloc.py | 7 +++----
>   1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/kms-test-brxalloc.py b/tests/kms-test-brxalloc.py
> index 2e3f6cb8b39e..f1902f3baf1d 100755
> --- a/tests/kms-test-brxalloc.py
> +++ b/tests/kms-test-brxalloc.py
> @@ -17,11 +17,10 @@ class BRxAllocTest(kmstest.KMSTest):
>       def main(self):
>           # This test requires usage of two CRTCs connected to the same VSPDL
>           # instance to test dynamic assignment of the BRU and BRS to pipelines.
> -        # This is only occurs on H3 ES2.0 (and M3N which we don't support yet).
> -        # Check the SoC model through sysfs as we can't detected it through the
> -        # DRM/KMS API.
> +        # This is only occurs on H3 ES2.0 and M3N. Check the SoC model through

    Not M3-N?

[...]

MBR, Sergei

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N
  2019-06-17  8:29 ` Sergei Shtylyov
@ 2019-06-17 20:26   ` Laurent Pinchart
  0 siblings, 0 replies; 4+ messages in thread
From: Laurent Pinchart @ 2019-06-17 20:26 UTC (permalink / raw)
  To: Sergei Shtylyov; +Cc: linux-renesas-soc, Kieran Bingham

Hi Sergei,

On Mon, Jun 17, 2019 at 11:29:52AM +0300, Sergei Shtylyov wrote:
> On 17.06.2019 3:35, Laurent Pinchart wrote:
> 
> > The BRU/BRS allocation test only covers the H3 ES2.0 SoC as that was the
> > only hardware platform supported by the DU driver that offered the
> > required features at the time the test was written. Now that M3-N is
> > supported in the DU driver, support it in the test script.
> > 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >   tests/kms-test-brxalloc.py | 7 +++----
> >   1 file changed, 3 insertions(+), 4 deletions(-)
> > 
> > diff --git a/tests/kms-test-brxalloc.py b/tests/kms-test-brxalloc.py
> > index 2e3f6cb8b39e..f1902f3baf1d 100755
> > --- a/tests/kms-test-brxalloc.py
> > +++ b/tests/kms-test-brxalloc.py
> > @@ -17,11 +17,10 @@ class BRxAllocTest(kmstest.KMSTest):
> >       def main(self):
> >           # This test requires usage of two CRTCs connected to the same VSPDL
> >           # instance to test dynamic assignment of the BRU and BRS to pipelines.
> > -        # This is only occurs on H3 ES2.0 (and M3N which we don't support yet).
> > -        # Check the SoC model through sysfs as we can't detected it through the
> > -        # DRM/KMS API.
> > +        # This is only occurs on H3 ES2.0 and M3N. Check the SoC model through
> 
>     Not M3-N?

Of course. I'll fix it.

> 
> [...]

-- 
Regards,

Laurent Pinchart

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N
  2019-06-17  0:35 [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N Laurent Pinchart
  2019-06-17  8:29 ` Sergei Shtylyov
@ 2019-06-18 21:33 ` Kieran Bingham
  1 sibling, 0 replies; 4+ messages in thread
From: Kieran Bingham @ 2019-06-18 21:33 UTC (permalink / raw)
  To: Laurent Pinchart, linux-renesas-soc

Hi Laurent,

On 17/06/2019 01:35, Laurent Pinchart wrote:
> The BRU/BRS allocation test only covers the H3 ES2.0 SoC as that was the
> only hardware platform supported by the DU driver that offered the
> required features at the time the test was written. Now that M3-N is
> supported in the DU driver, support it in the test script.
> 
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>  tests/kms-test-brxalloc.py | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/kms-test-brxalloc.py b/tests/kms-test-brxalloc.py
> index 2e3f6cb8b39e..f1902f3baf1d 100755
> --- a/tests/kms-test-brxalloc.py
> +++ b/tests/kms-test-brxalloc.py
> @@ -17,11 +17,10 @@ class BRxAllocTest(kmstest.KMSTest):
>      def main(self):
>          # This test requires usage of two CRTCs connected to the same VSPDL
>          # instance to test dynamic assignment of the BRU and BRS to pipelines.
> -        # This is only occurs on H3 ES2.0 (and M3N which we don't support yet).
> -        # Check the SoC model through sysfs as we can't detected it through the
> -        # DRM/KMS API.
> +        # This is only occurs on H3 ES2.0 and M3N. Check the SoC model through
> +        # sysfs as we can't detected it through the DRM/KMS API.
>          soc = open("/sys/devices/soc0/soc_id", "rb").read().strip().decode()
> -        if soc != "r8a7795":
> +        if soc != "r8a7795" and soc != "r8a77965":

To be a bit more pythonic, you could write;
           if soc not in ["r8a7795", "r8a77965"]:

But I don't think this list is going to be extended any time soon so it
doesn't really matter.

Up to you either way,

Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>


>              self.skip("VSPDL (BRU+BRS) not available")
>              return
>  
> 

-- 
Regards
--
Kieran

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-06-18 21:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-17  0:35 [kms-tests] [PATCH] tests: Extend BRU/BRS allocation test to cover M3-N Laurent Pinchart
2019-06-17  8:29 ` Sergei Shtylyov
2019-06-17 20:26   ` Laurent Pinchart
2019-06-18 21:33 ` Kieran Bingham

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.