linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Sebastian Fricke <sebastian.fricke@collabora.com>,
	linux-media@vger.kernel.org,
	Nas Chung <nas.chung@chipsnmedia.com>,
	Robert Beckett <bob.beckett@collabora.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel@collabora.com, nicolas.dufresne@collabora.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 4/6] media: chips-media: wave5: Add TODO file
Date: Mon, 12 Dec 2022 15:30:56 +0100	[thread overview]
Message-ID: <481d69d1-e073-1b77-e222-3b317c1a6d0f@xs4all.nl> (raw)
In-Reply-To: <20221207121350.66217-5-sebastian.fricke@collabora.com>

On 07/12/2022 13:13, Sebastian Fricke wrote:
> From: Nas Chung <nas.chung@chipsnmedia.com>
> 
> Add a TODO file with remaining elements to be improved/added.
> 
> Signed-off-by: Robert Beckett <bob.beckett@collabora.com>
> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com>
> Signed-off-by: Nas Chung <nas.chung@chipsnmedia.com>
> ---
>  drivers/media/platform/chips-media/wave5/TODO | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
>  create mode 100644 drivers/media/platform/chips-media/wave5/TODO
> 
> diff --git a/drivers/media/platform/chips-media/wave5/TODO b/drivers/media/platform/chips-media/wave5/TODO
> new file mode 100644
> index 000000000000..2164fd071a56
> --- /dev/null
> +++ b/drivers/media/platform/chips-media/wave5/TODO
> @@ -0,0 +1,18 @@
> +* Handle interrupts better
> +
> +Currently the interrupt handling uses an unusual design employing a kfifo to
> +transfer irq status to irq thread. This was done as a work around for dropped
> +interrupts seen with IRQF_ONESHOT based handling.
> +
> +This needs further investigation and fixing properly, with the aid of
> +C&M.
> +
> +* power management handling - add (runtime_)suspen/resume cb where the clock is enabled
> +
> +* revise logic of wave5_vpu_(dec/enc)_register_framebuffer
> +
> +* check if the  normal kernel endianness/__swab32 routines are sufficient. (instead of the ones
> +  implemented in the driver)
> +
> +* Adjust STREAMON routine for the stateful decoder to adhere to the API, which
> +  declares that STREAMON can be called before source buffers have been queued.

A TODO file doesn't belong in a non-staging driver.

So either it should remain in staging if this is serious enough (and I'm a bit
worried about the last item here!), or it should be documented in comments in
the driver in the appropriate places.

Note that the "revise logic" item doesn't explain the reason why that should be
done.

Regards,

	Hans

  reply	other threads:[~2022-12-12 14:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221207121350.66217-1-sebastian.fricke@collabora.com>
2022-12-07 12:13 ` [PATCH v11 1/6] media: platform: chips-media: Move Coda to separate folder Sebastian Fricke
2022-12-07 12:54   ` Philipp Zabel
2022-12-07 20:44   ` kernel test robot
2022-12-07 12:13 ` [PATCH v11 2/6] media: chips-media: wave5: Add vpuapi layer Sebastian Fricke
2022-12-07 13:05   ` AngeloGioacchino Del Regno
2022-12-15 13:31     ` Sebastian Fricke
2022-12-07 12:13 ` [PATCH v11 3/6] media: chips-media: wave5: Add the v4l2 layer Sebastian Fricke
2022-12-12 14:19   ` Hans Verkuil
2023-04-26 13:22     ` Nicolas Dufresne
2023-04-26 14:44   ` Nicolas Dufresne
2022-12-07 12:13 ` [PATCH v11 4/6] media: chips-media: wave5: Add TODO file Sebastian Fricke
2022-12-12 14:30   ` Hans Verkuil [this message]
2022-12-07 12:13 ` [PATCH v11 5/6] dt-bindings: media: wave5: add yaml devicetree bindings Sebastian Fricke
2022-12-07 12:31   ` Krzysztof Kozlowski
2022-12-07 13:17     ` Krzysztof Kozlowski
2022-12-07 15:09     ` Sebastian Fricke
2022-12-07 15:27       ` Krzysztof Kozlowski
2022-12-12 11:32         ` Sebastian Fricke
2023-09-04  6:25     ` Sebastian Fricke
2023-09-04  7:53       ` Krzysztof Kozlowski
2022-12-07 12:13 ` [PATCH v11 6/6] media: chips-media: wave5: Add wave5 driver to maintainers file Sebastian Fricke
2022-12-08  5:29   ` kernel test robot

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=481d69d1-e073-1b77-e222-3b317c1a6d0f@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=bob.beckett@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=sebastian.fricke@collabora.com \
    /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;
as well as URLs for NNTP newsgroup(s).