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@xxxxxxxxxxxxxxxx> > > --- > > 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
