All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@google.com>
To: "kyrie.wu" <kyrie.wu@mediatek.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Bin Liu <bin.liu@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Tzung-Bi Shih <tzungbi@chromium.org>,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Tomasz Figa <tfiga@chromium.org>,
	xia.jiang@mediatek.com, maoguang.meng@mediatek.com,
	srv_heupstream@mediatek.com
Subject: Re: [PATCH v2,9/9] media: mtk-jpegenc: Refactor jpegenc device run interface
Date: Tue, 6 Jul 2021 19:01:00 +0800	[thread overview]
Message-ID: <CA+Px+wWkS-PMVa4DGc9df8p8QLDFEvQXbOhYJb-rqk5P-C_+7A@mail.gmail.com> (raw)
In-Reply-To: <1625038079-25815-10-git-send-email-kyrie.wu@mediatek.com>

On Wed, Jun 30, 2021 at 3:32 PM kyrie.wu <kyrie.wu@mediatek.com> wrote:
> modify jpegenc device run func interface and add worker for encode
The description makes less sense.

> +static void mtk_jpegenc_worker(struct work_struct *work)
>  {
> -       struct mtk_jpeg_ctx *ctx = priv;
> +       struct mtk_jpeg_ctx *ctx = container_of(work, struct mtk_jpeg_ctx,
> +               jpeg_work);
>         struct mtk_jpeg_dev *jpeg = ctx->jpeg;
> +       struct mtk_jpeg_dev *comp_jpeg[MTK_JPEGENC_HW_MAX];
>         struct vb2_v4l2_buffer *src_buf, *dst_buf;
>         enum vb2_buffer_state buf_state = VB2_BUF_STATE_ERROR;
>         unsigned long flags;
> -       int ret;
> +       struct mtk_jpeg_src_buf *jpeg_src_buf, *jpeg_dst_buf;
> +       int ret, i, hw_id = 0;
hw_id doesn't need to be initialized.

> +retry_select:
> +       hw_id = mtk_jpeg_select_hw(ctx);
> +       if (hw_id < 0) {
> +               ret = wait_event_interruptible(jpeg->hw_wq,
> +                               (atomic_read(hw_rdy[0]) ||
> +                               atomic_read(hw_rdy[1])) > 0);
Hard-coded refers to hw_rdy[0] and hw_rdy[1] here?

> -       mtk_jpeg_enc_reset(jpeg->reg_base);
> -
> -       mtk_jpeg_set_enc_src(ctx, jpeg->reg_base, &src_buf->vb2_buf);
> -       mtk_jpeg_set_enc_dst(ctx, jpeg->reg_base, &dst_buf->vb2_buf);
> -       mtk_jpeg_set_enc_params(ctx, jpeg->reg_base);
> -       mtk_jpeg_enc_start(jpeg->reg_base);
> -       spin_unlock_irqrestore(&jpeg->hw_lock, flags);
> +       spin_lock_irqsave(&comp_jpeg[hw_id]->hw_lock, flags);
> +       mtk_jpeg_enc_reset(comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_set_enc_dst(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &dst_buf->vb2_buf);
> +       mtk_jpeg_set_enc_src(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &src_buf->vb2_buf);
> +       mtk_jpeg_set_enc_params(ctx, comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_enc_start(comp_jpeg[hw_id]->reg_base[0]);
Why it uses reg_base[0]?

WARNING: multiple messages have this Message-ID (diff)
From: Tzung-Bi Shih <tzungbi@google.com>
To: "kyrie.wu" <kyrie.wu@mediatek.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	 Rob Herring <robh+dt@kernel.org>, Bin Liu <bin.liu@mediatek.com>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	Tzung-Bi Shih <tzungbi@chromium.org>,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	 linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-mediatek@lists.infradead.org,
	Tomasz Figa <tfiga@chromium.org>,
	 xia.jiang@mediatek.com, maoguang.meng@mediatek.com,
	 srv_heupstream@mediatek.com
Subject: Re: [PATCH v2, 9/9] media: mtk-jpegenc: Refactor jpegenc device run interface
Date: Tue, 6 Jul 2021 19:01:00 +0800	[thread overview]
Message-ID: <CA+Px+wWkS-PMVa4DGc9df8p8QLDFEvQXbOhYJb-rqk5P-C_+7A@mail.gmail.com> (raw)
In-Reply-To: <1625038079-25815-10-git-send-email-kyrie.wu@mediatek.com>

On Wed, Jun 30, 2021 at 3:32 PM kyrie.wu <kyrie.wu@mediatek.com> wrote:
> modify jpegenc device run func interface and add worker for encode
The description makes less sense.

> +static void mtk_jpegenc_worker(struct work_struct *work)
>  {
> -       struct mtk_jpeg_ctx *ctx = priv;
> +       struct mtk_jpeg_ctx *ctx = container_of(work, struct mtk_jpeg_ctx,
> +               jpeg_work);
>         struct mtk_jpeg_dev *jpeg = ctx->jpeg;
> +       struct mtk_jpeg_dev *comp_jpeg[MTK_JPEGENC_HW_MAX];
>         struct vb2_v4l2_buffer *src_buf, *dst_buf;
>         enum vb2_buffer_state buf_state = VB2_BUF_STATE_ERROR;
>         unsigned long flags;
> -       int ret;
> +       struct mtk_jpeg_src_buf *jpeg_src_buf, *jpeg_dst_buf;
> +       int ret, i, hw_id = 0;
hw_id doesn't need to be initialized.

> +retry_select:
> +       hw_id = mtk_jpeg_select_hw(ctx);
> +       if (hw_id < 0) {
> +               ret = wait_event_interruptible(jpeg->hw_wq,
> +                               (atomic_read(hw_rdy[0]) ||
> +                               atomic_read(hw_rdy[1])) > 0);
Hard-coded refers to hw_rdy[0] and hw_rdy[1] here?

> -       mtk_jpeg_enc_reset(jpeg->reg_base);
> -
> -       mtk_jpeg_set_enc_src(ctx, jpeg->reg_base, &src_buf->vb2_buf);
> -       mtk_jpeg_set_enc_dst(ctx, jpeg->reg_base, &dst_buf->vb2_buf);
> -       mtk_jpeg_set_enc_params(ctx, jpeg->reg_base);
> -       mtk_jpeg_enc_start(jpeg->reg_base);
> -       spin_unlock_irqrestore(&jpeg->hw_lock, flags);
> +       spin_lock_irqsave(&comp_jpeg[hw_id]->hw_lock, flags);
> +       mtk_jpeg_enc_reset(comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_set_enc_dst(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &dst_buf->vb2_buf);
> +       mtk_jpeg_set_enc_src(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &src_buf->vb2_buf);
> +       mtk_jpeg_set_enc_params(ctx, comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_enc_start(comp_jpeg[hw_id]->reg_base[0]);
Why it uses reg_base[0]?

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Tzung-Bi Shih <tzungbi@google.com>
To: "kyrie.wu" <kyrie.wu@mediatek.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	 Rob Herring <robh+dt@kernel.org>, Bin Liu <bin.liu@mediatek.com>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	Tzung-Bi Shih <tzungbi@chromium.org>,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	 linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-mediatek@lists.infradead.org,
	Tomasz Figa <tfiga@chromium.org>,
	 xia.jiang@mediatek.com, maoguang.meng@mediatek.com,
	 srv_heupstream@mediatek.com
Subject: Re: [PATCH v2, 9/9] media: mtk-jpegenc: Refactor jpegenc device run interface
Date: Tue, 6 Jul 2021 19:01:00 +0800	[thread overview]
Message-ID: <CA+Px+wWkS-PMVa4DGc9df8p8QLDFEvQXbOhYJb-rqk5P-C_+7A@mail.gmail.com> (raw)
In-Reply-To: <1625038079-25815-10-git-send-email-kyrie.wu@mediatek.com>

On Wed, Jun 30, 2021 at 3:32 PM kyrie.wu <kyrie.wu@mediatek.com> wrote:
> modify jpegenc device run func interface and add worker for encode
The description makes less sense.

> +static void mtk_jpegenc_worker(struct work_struct *work)
>  {
> -       struct mtk_jpeg_ctx *ctx = priv;
> +       struct mtk_jpeg_ctx *ctx = container_of(work, struct mtk_jpeg_ctx,
> +               jpeg_work);
>         struct mtk_jpeg_dev *jpeg = ctx->jpeg;
> +       struct mtk_jpeg_dev *comp_jpeg[MTK_JPEGENC_HW_MAX];
>         struct vb2_v4l2_buffer *src_buf, *dst_buf;
>         enum vb2_buffer_state buf_state = VB2_BUF_STATE_ERROR;
>         unsigned long flags;
> -       int ret;
> +       struct mtk_jpeg_src_buf *jpeg_src_buf, *jpeg_dst_buf;
> +       int ret, i, hw_id = 0;
hw_id doesn't need to be initialized.

> +retry_select:
> +       hw_id = mtk_jpeg_select_hw(ctx);
> +       if (hw_id < 0) {
> +               ret = wait_event_interruptible(jpeg->hw_wq,
> +                               (atomic_read(hw_rdy[0]) ||
> +                               atomic_read(hw_rdy[1])) > 0);
Hard-coded refers to hw_rdy[0] and hw_rdy[1] here?

> -       mtk_jpeg_enc_reset(jpeg->reg_base);
> -
> -       mtk_jpeg_set_enc_src(ctx, jpeg->reg_base, &src_buf->vb2_buf);
> -       mtk_jpeg_set_enc_dst(ctx, jpeg->reg_base, &dst_buf->vb2_buf);
> -       mtk_jpeg_set_enc_params(ctx, jpeg->reg_base);
> -       mtk_jpeg_enc_start(jpeg->reg_base);
> -       spin_unlock_irqrestore(&jpeg->hw_lock, flags);
> +       spin_lock_irqsave(&comp_jpeg[hw_id]->hw_lock, flags);
> +       mtk_jpeg_enc_reset(comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_set_enc_dst(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &dst_buf->vb2_buf);
> +       mtk_jpeg_set_enc_src(ctx,
> +                            comp_jpeg[hw_id]->reg_base[0],
> +                            &src_buf->vb2_buf);
> +       mtk_jpeg_set_enc_params(ctx, comp_jpeg[hw_id]->reg_base[0]);
> +       mtk_jpeg_enc_start(comp_jpeg[hw_id]->reg_base[0]);
Why it uses reg_base[0]?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-06 11:01 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  7:27 [PATCH v2,0/9] Support jpeg encode for MT8195 kyrie.wu
2021-06-30  7:27 ` kyrie.wu
2021-06-30  7:27 ` [PATCH v2, 1/9] dt-bindings: mediatek: Add mediatek, mt8195-jpgenc compatible kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-06-30  7:27 ` [PATCH v2,2/9] media: mtk-jpegenc: Add MT8195 JPEG venc driver kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-06-30  7:27 ` [PATCH v2,3/9] media: mtk-jpegenc: remove redundant code of irq kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-09  9:07     ` Tomasz Figa
2021-07-09  9:07       ` Tomasz Figa
2021-07-09  9:07       ` Tomasz Figa
2021-06-30  7:27 ` [PATCH v2,4/9] media: mtk-jpegenc: Refactor jpeg clock interface kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-09  9:20   ` Tomasz Figa
2021-07-09  9:20     ` Tomasz Figa
2021-07-09  9:20     ` Tomasz Figa
2021-06-30  7:27 ` [PATCH v2, 5/9] media: mtk-jpegenc: Generalize jpeg encode irq interfaces kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-09 10:20   ` [PATCH v2,5/9] " Tomasz Figa
2021-07-09 10:20     ` Tomasz Figa
2021-07-09 10:20     ` Tomasz Figa
2021-06-30  7:27 ` [PATCH v2, 6/9] media: mtk-jpegenc: Generalize jpegenc HW timeout interfaces kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` [PATCH v2,6/9] " Tzung-Bi Shih
2021-07-06 11:00     ` [PATCH v2, 6/9] " Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-06-30  7:27 ` [PATCH v2, 7/9] media: mtk-jpegenc: Use component framework to manage each hardware information kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` [PATCH v2,7/9] " Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-06-30  7:27 ` [PATCH v2, 8/9] media: mtk-jpegenc: Generalize jpegenc HW operations interfaces kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:00   ` [PATCH v2,8/9] " Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-07-06 11:00     ` Tzung-Bi Shih
2021-06-30  7:27 ` [PATCH v2, 9/9] media: mtk-jpegenc: Refactor jpegenc device run interface kyrie.wu
2021-06-30  7:27   ` kyrie.wu
2021-07-06 11:01   ` Tzung-Bi Shih [this message]
2021-07-06 11:01     ` Tzung-Bi Shih
2021-07-06 11:01     ` Tzung-Bi Shih
2021-07-06 11:00 ` [PATCH v2,0/9] Support jpeg encode for MT8195 Tzung-Bi Shih
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-06 11:00   ` Tzung-Bi Shih
2021-07-09  8:27   ` Tomasz Figa
2021-07-09  8:27     ` Tomasz Figa
2021-07-09  8:27     ` Tomasz Figa
2021-07-09 10:26 ` Tomasz Figa
2021-07-09 10:26   ` Tomasz Figa
2021-07-09 10:26   ` Tomasz Figa

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=CA+Px+wWkS-PMVa4DGc9df8p8QLDFEvQXbOhYJb-rqk5P-C_+7A@mail.gmail.com \
    --to=tzungbi@google.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=bin.liu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=kyrie.wu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=maoguang.meng@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srv_heupstream@mediatek.com \
    --cc=tfiga@chromium.org \
    --cc=tzungbi@chromium.org \
    --cc=xia.jiang@mediatek.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 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.