From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 07/14] staging: media: tegra-vde: Add some clarifying comments
Date: Sat, 18 Aug 2018 15:50:17 +0300 [thread overview]
Message-ID: <5081449.StsSdamf0J@dimapc> (raw)
In-Reply-To: <20180813145027.16346-8-thierry.reding@gmail.com>
On Monday, 13 August 2018 17:50:20 MSK Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Add some comments specifying what tables are being set up in VRAM.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/staging/media/tegra-vde/tegra-vde.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/staging/media/tegra-vde/tegra-vde.c
> b/drivers/staging/media/tegra-vde/tegra-vde.c index
> 0adc603fa437..41cf86dc5dbd 100644
> --- a/drivers/staging/media/tegra-vde/tegra-vde.c
> +++ b/drivers/staging/media/tegra-vde/tegra-vde.c
> @@ -271,6 +271,7 @@ static void tegra_vde_setup_iram_tables(struct tegra_vde
> *vde, unsigned int i, k;
> size_t size;
>
> + /* clear H256RefPicList */
> size = num_ref_pics * 4 * 8;
> memset(vde->iram, 0, size);
H256? Is it a typo?
>
> @@ -453,6 +454,7 @@ static int tegra_vde_setup_hw_context(struct tegra_vde
> *vde, VDE_WR(0x00000000, vde->bsev + 0x98);
> VDE_WR(0x00000060, vde->bsev + 0x9C);
>
> + /* clear H264MB2SliceGroupMap, assuming no FMO */
> memset(vde->iram + 1024, 0, macroblocks_nb / 2);
>
> tegra_setup_frameidx(vde, dpb_frames, ctx->dpb_frames_nb,
> @@ -480,6 +482,8 @@ static int tegra_vde_setup_hw_context(struct tegra_vde
> *vde, if (err)
> return err;
>
> + /* upload H264MB2SliceGroupMap */
> + /* XXX don't hardcode map size? */
> value = (0x20 << 26) | (0 << 25) | ((4096 >> 2) & 0x1fff);
> err = tegra_vde_push_to_bsev_icmdqueue(vde, value, false);
> if (err)
> @@ -492,6 +496,7 @@ static int tegra_vde_setup_hw_context(struct tegra_vde
> *vde, if (err)
> return err;
>
> + /* clear H264MBInfo XXX don't hardcode size */
> value = (0x21 << 26) | ((240 & 0x1fff) << 12) | (0x54c & 0xfff);
> err = tegra_vde_push_to_bsev_icmdqueue(vde, 0x840F054C, false);
> if (err)
> @@ -499,6 +504,16 @@ static int tegra_vde_setup_hw_context(struct tegra_vde
> *vde,
>
> size = num_ref_pics * 4 * 8;
>
> + /* clear H264RefPicList */
#if 0
> + value = (0x21 << 26) | (((size >> 2) & 0x1fff) << 12) | 0xE34;
> +
> + err = tegra_vde_push_to_bsev_icmdqueue(vde, value, false);
> + if (err)
> + return err;
#endif
Is it supposed to do the same as "clear H256RefPicList -> memset(vde->iram, 0,
size)" above?
> +
> + /* upload H264RefPicList */
> value = (0x20 << 26) | (0x0 << 25) | ((size >> 2) & 0x1fff);
> err = tegra_vde_push_to_bsev_icmdqueue(vde, value, false);
> if (err)
> @@ -584,7 +599,11 @@ static int tegra_vde_setup_hw_context(struct tegra_vde
> *vde,
>
> tegra_vde_mbe_set_0xa_reg(vde, 0, 0x000009FC);
> tegra_vde_mbe_set_0xa_reg(vde, 2, 0x61DEAD00);
> +#if 0
> + tegra_vde_mbe_set_0xa_reg(vde, 4, dpb_frames[0].aux_addr); /* 0x62DEAD00
> */ +#else
> tegra_vde_mbe_set_0xa_reg(vde, 4, 0x62DEAD00);
> +#endif
This doesn't really clarify much, let's drop this chunk for now.
> tegra_vde_mbe_set_0xa_reg(vde, 6, 0x63DEAD00);
> tegra_vde_mbe_set_0xa_reg(vde, 8, dpb_frames[0].aux_addr);
next prev parent reply other threads:[~2018-08-18 12:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 14:50 [PATCH 00/14] staging: media: tegra-vdea: Add Tegra124 support Thierry Reding
2018-08-13 14:50 ` [PATCH 01/14] staging: media: tegra-vde: Support BSEV clock and reset Thierry Reding
2018-08-13 15:09 ` Dmitry Osipenko
2018-08-14 14:21 ` Thierry Reding
2018-08-14 15:05 ` Dmitry Osipenko
2018-08-14 15:16 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 02/14] staging: media: tegra-vde: Support reference picture marking Thierry Reding
2018-08-18 12:48 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 03/14] staging: media: tegra-vde: Prepare for interlacing support Thierry Reding
2018-08-18 12:48 ` Dmitry Osipenko
2018-08-30 8:56 ` Dan Carpenter
2018-08-13 14:50 ` [PATCH 04/14] staging: media: tegra-vde: Use DRM/KMS framebuffer modifiers Thierry Reding
2018-08-18 12:53 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 05/14] staging: media: tegra-vde: Properly mark invalid entries Thierry Reding
2018-08-18 12:45 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 06/14] staging: media: tegra-vde: Print out invalid FD Thierry Reding
2018-08-18 12:45 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 07/14] staging: media: tegra-vde: Add some clarifying comments Thierry Reding
2018-08-18 12:50 ` Dmitry Osipenko [this message]
2018-08-13 14:50 ` [PATCH 08/14] staging: media: tegra-vde: Track struct device * Thierry Reding
2018-08-18 12:49 ` Dmitry Osipenko
2018-08-18 15:39 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 09/14] staging: media: tegra-vde: Add IOMMU support Thierry Reding
2018-08-18 12:50 ` Dmitry Osipenko
2018-08-18 13:07 ` Dmitry Osipenko
2018-08-18 13:29 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 10/14] staging: media: tegra-vde: Keep VDE in reset when unused Thierry Reding
2018-08-18 12:50 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 11/14] ARM: tegra: Enable VDE on Tegra124 Thierry Reding
2018-08-18 12:45 ` Dmitry Osipenko
2018-08-13 14:50 ` [PATCH 12/14] ARM: tegra: Add BSEV clock and reset for VDE on Tegra20 Thierry Reding
2018-08-13 14:50 ` [PATCH 13/14] ARM: tegra: Add BSEV clock and reset for VDE on Tegra30 Thierry Reding
2018-08-13 14:50 ` [PATCH 14/14] ARM: tegra: Enable SMMU for VDE on Tegra124 Thierry Reding
2018-08-18 12:45 ` Dmitry Osipenko
2018-09-03 12:18 ` [PATCH 00/14] staging: media: tegra-vdea: Add Tegra124 support Hans Verkuil
2018-09-03 13:12 ` Thierry Reding
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=5081449.StsSdamf0J@dimapc \
--to=digetx@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=thierry.reding@gmail.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).