From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Jason-ch Chen (陳建豪)" <Jason-ch.Chen@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Shawn Sung (宋孝謙)" <Shawn.Sung@mediatek.com>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RESEND, v6 6/8] mailbox: mediatek: Add CMDQ secure mailbox driver
Date: Mon, 17 Jun 2024 07:18:21 +0000 [thread overview]
Message-ID: <ed98af2c1fcf878a83dff4b9667db57c3412d708.camel@mediatek.com> (raw)
In-Reply-To: <20240526144443.14345-7-jason-jh.lin@mediatek.com>
Hi, Jason:
On Sun, 2024-05-26 at 22:44 +0800, Jason-JH.Lin wrote:
> To support secure video path feature, GCE have to read/write registgers
> in the secure world. GCE will enable the secure access permission to the
> HW who wants to access the secure content buffer.
>
> Add CMDQ secure mailbox driver to make CMDQ client user is able to
> sending their HW settings to the secure world. So that GCE can execute
> all instructions to configure HW in the secure world.
>
> TODO:
> 1. Squash cmdq_sec_task_exec_work() into cmdq_sec_mbox_send_data().
> 2. Call into TEE to query cookie instead of using shared memory in
> cmdq_sec_get_cookie().
> 3. Register shared memory as command buffer instead of copying normal
> command buffer to IWC shared memory.
> 4. Use SOFTDEP to make cmdq_sec_probe later than OPTEE loaded and then
> move cmdq_sec_session_init into cmdq_sec_probe().
> 5. Remove timeout detection in cmdq_sec_session_send().
>
> Signed-off-by: Jason-JH.Lin <jason-jh.lin@mediatek.com>
> Signed-off-by: Hsiao Chien Sung <shawn.sung@mediatek.com>
> ---
[snip]
> +static int cmdq_sec_irq_notify_start(struct cmdq_sec *cmdq)
> +{
> + int err;
> + dma_addr_t dma_addr;
> + u64 *inst = NULL;
> +
> + if (cmdq->notify_run)
> + return 0;
> +
> + cmdq->notify_clt.dev = cmdq->pdata->mbox->dev;
> + cmdq->notify_clt.rx_callback = cmdq_sec_irq_notify_callback;
> + cmdq->notify_clt.tx_block = false;
> + cmdq->notify_clt.knows_txdone = true;
> + cmdq->notify_chan = mbox_request_channel(&cmdq->notify_clt, 0);
When playing secure video, video decoder driver would have interrupt both in normal world and secure world [1].
I guess cmdq driver could also have both interrupt in normal world and secure world.
If so, it's not necessary to create a channel to wait SW token.
[1] https://patchwork.kernel.org/project/linux-mediatek/patch/20240516122102.16379-20-yunfei.dong@mediatek.com/
Regards,
CK
> + if (IS_ERR(cmdq->notify_chan)) {
> + dev_err(&cmdq->dev, "failed to request channel\n");
> + return -ENODEV;
> + }
> +
> + cmdq->clt_pkt.va_base = kzalloc(PAGE_SIZE, GFP_KERNEL);
> + if (!cmdq->clt_pkt.va_base)
> + return -ENOMEM;
> +
> + cmdq->clt_pkt.buf_size = PAGE_SIZE;
> +
> + dma_addr = dma_map_single(cmdq->pdata->mbox->dev, cmdq->clt_pkt.va_base,
> + cmdq->clt_pkt.buf_size, DMA_TO_DEVICE);
> + if (dma_mapping_error(cmdq->pdata->mbox->dev, dma_addr)) {
> + dev_err(cmdq->pdata->mbox->dev, "dma map failed, size=%lu\n", PAGE_SIZE);
> + kfree(cmdq->clt_pkt.va_base);
> + return -ENOMEM;
> + }
> + cmdq->clt_pkt.pa_base = dma_addr;
> +
> + INIT_WORK(&cmdq->irq_notify_work, cmdq_sec_irq_notify_work);
> +
> + /* generate irq notify loop command */
> + inst = (u64 *)cmdq->clt_pkt.va_base;
> + *inst = CMDQ_WFE_CMD(cmdq->pdata->cmdq_event);
> + inst++;
> + *inst = CMDQ_EOC_CMD;
> + inst++;
> + *inst = CMDQ_JUMP_CMD(cmdq->clt_pkt.pa_base, cmdq->pdata->shift);
> + inst++;
> + cmdq->clt_pkt.cmd_buf_size += CMDQ_INST_SIZE * 3;
> + cmdq->clt_pkt.loop = true;
> +
> + dma_sync_single_for_device(cmdq->pdata->mbox->dev,
> + cmdq->clt_pkt.pa_base,
> + cmdq->clt_pkt.cmd_buf_size,
> + DMA_TO_DEVICE);
> + err = mbox_send_message(cmdq->notify_chan, &cmdq->clt_pkt);
> + mbox_client_txdone(cmdq->notify_chan, 0);
> + if (err < 0) {
> + dev_err(&cmdq->dev, "%s failed:%d", __func__, err);
> + dma_unmap_single(cmdq->pdata->mbox->dev, cmdq->clt_pkt.pa_base,
> + cmdq->clt_pkt.buf_size, DMA_TO_DEVICE);
> + kfree(cmdq->clt_pkt.va_base);
> + mbox_free_channel(cmdq->notify_chan);
> +
> + return err;
> + }
> +
> + cmdq->notify_run = true;
> + dev_dbg(&cmdq->dev, "%s success!", __func__);
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2024-06-17 7:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 14:44 [PATCH RESEND,v6 0/8] Add CMDQ secure driver for SVP Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 1/8] dt-bindings: gce: mt8195: Add CMDQ_SYNC_TOKEN_SECURE_THR_EOF event id Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 2/8] dt-bindings: mailbox: Add property for CMDQ secure driver Jason-JH.Lin
2024-05-26 16:13 ` Rob Herring (Arm)
2024-05-27 5:21 ` Jason-JH Lin (林睿祥)
2024-05-27 17:36 ` Conor Dooley
2024-05-28 14:38 ` Jason-JH Lin (林睿祥)
2024-05-28 14:59 ` Conor Dooley
2024-05-28 15:10 ` Jason-JH Lin (林睿祥)
2024-05-26 14:44 ` [PATCH RESEND,v6 3/8] soc: mediatek: cmdq: Add cmdq_pkt_logic_command to support math operation Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 4/8] mailbox: mtk-cmdq: Support GCE loop packets in interrupt handler Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 5/8] mailbox: mediatek: Move reuseable definition to header for secure driver Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 6/8] mailbox: mediatek: Add CMDQ secure mailbox driver Jason-JH.Lin
2024-05-27 3:44 ` [PATCH RESEND, v6 " CK Hu (胡俊光)
2024-05-27 5:04 ` Jason-JH Lin (林睿祥)
2024-05-28 2:19 ` CK Hu (胡俊光)
2024-05-29 14:33 ` Jason-JH Lin (林睿祥)
2024-05-28 3:17 ` CK Hu (胡俊光)
2024-05-28 15:33 ` Jason-JH Lin (林睿祥)
2024-06-17 7:18 ` CK Hu (胡俊光) [this message]
2024-05-26 14:44 ` [PATCH RESEND,v6 7/8] mailbox: mediatek: Add secure CMDQ driver support for CMDQ driver Jason-JH.Lin
2024-05-26 14:44 ` [PATCH RESEND,v6 8/8] soc: mediatek: mtk-cmdq: Add secure cmdq_pkt APIs Jason-JH.Lin
2024-05-28 3:01 ` CK Hu (胡俊光)
2024-05-28 15:33 ` Jason-JH Lin (林睿祥)
2024-05-29 1:58 ` CK Hu (胡俊光)
2024-05-29 14:49 ` Jason-JH Lin (林睿祥)
2024-06-13 10:58 ` [PATCH RESEND,v6 0/8] Add CMDQ secure driver for SVP Pavel Machek
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=ed98af2c1fcf878a83dff4b9667db57c3412d708.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Jason-JH.Lin@mediatek.com \
--cc=Jason-ch.Chen@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Shawn.Sung@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
/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).