From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Takanari Hayama <taki@igel.co.jp>
Cc: linux-renesas-soc@vger.kernel.org,
laurent.pinchart@ideasonboard.com,
kieran.bingham+renesas@ideasonboard.com
Subject: Re: [PATCH 1/3] tests: Support enum property type
Date: Mon, 4 Jul 2022 12:00:46 +0300 [thread overview]
Message-ID: <743e8135-391b-e00c-2493-4b4052a66ea3@gmail.com> (raw)
In-Reply-To: <546B54F4-5931-4CAE-A910-A6ED2F3C311A@igel.co.jp>
On 7/4/22 11:53 AM, Takanari Hayama wrote:
[...]
>>> Add a support for enum property type to AtomicRequest.
>>>
>>> Signed-off-by: Takanari Hayama <taki@igel.co.jp>
>>> ---
>>> tests/kmstest.py | 12 +++++++++++-
>>> 1 file changed, 11 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tests/kmstest.py b/tests/kmstest.py
>>> index 11cc328b5b32..224c160e32fa 100755
>>> --- a/tests/kmstest.py
>>> +++ b/tests/kmstest.py
>>> @@ -269,8 +269,18 @@ class AtomicRequest(pykms.AtomicReq):
>>>
>>> min, max = prop.values
>>> v = min + int((max - min) * int(v[:-1]) / 100)
>>> - else:
>>> + elif v.isnumeric():
>>> v = int(v)
>>> + else:
>>> + prop = obj.get_prop(k)
>>> + if prop.type != pykms.PropertyType.Enum:
>>> + raise RuntimeError(f'Unsupported property type {prop.type} for value {v}')
>>> + for value, mode in prop.enums.items():
>>> + if mode == v:
>>> + v = value
>>> + break
>>> + else:
>>
>> Hm, doesn't seem to be correctly aligned?
>
> That ‘else’ is for ‘for’-loop. Am I missing something here?
Hm, I don't really know Python, can it actually have else for
a loop?
>>> + raise RuntimeError(f'Enum value with name "{v}" not found in property {k}')
>>>
>>> if not isinstance(v, int):
>>> raise RuntimeError(f'Unsupported value type {type(v)} for property {k}')
MBR, Sergey
[...]
next prev parent reply other threads:[~2022-07-04 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:56 [PATCH 0/3] Test pixel blend mode Takanari Hayama
2022-07-04 2:56 ` [PATCH 1/3] tests: Support enum property type Takanari Hayama
2022-07-04 8:43 ` Sergei Shtylyov
2022-07-04 8:53 ` Takanari Hayama
2022-07-04 9:00 ` Sergei Shtylyov [this message]
2022-07-04 9:13 ` Takanari Hayama
2022-07-31 16:00 ` Laurent Pinchart
2022-07-31 16:18 ` Laurent Pinchart
2022-08-01 8:29 ` Takanari Hayama
2022-07-04 2:56 ` [PATCH 2/3] kmstest: Support specifying pixel blend mode for planes Takanari Hayama
2022-07-31 16:02 ` Laurent Pinchart
2022-07-04 2:56 ` [PATCH 3/3] tests: Add pixel blend mode test Takanari Hayama
2022-07-31 18:50 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=743e8135-391b-e00c-2493-4b4052a66ea3@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=taki@igel.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox