From: kholk11@gmail.com
To: stanimir.varbanov@linaro.org
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
linux-media@vger.kernel.org, kholk11@gmail.com,
marijns95@gmail.com, konradybcio@gmail.com,
martin.botka1@gmail.com, linux-arm-msm@vger.kernel.org,
phone-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Qualcomm Venus enablement for SDM630/636/660
Date: Sat, 26 Sep 2020 14:54:09 +0200 [thread overview]
Message-ID: <20200926125412.13024-1-kholk11@gmail.com> (raw)
From: AngeloGioacchino Del Regno <kholk11@gmail.com>
In this patch series, I am enabling the Venus video (enc/dec)oding
functionality on SDM630, SDM636, SDM660 and their SDA variants.
To reliably achieve this, commonizing most of the v3/v4 pm_helper
functions (while keeping compatibility with the previous bindings)
seemed to be totally legit, as (almost) the whole logic that's been
introduced in the v4 helpers does actually apply to all (in my knowledge)
of the SoCs that are currently needing the v3 ops to *at least*
optimize the power consumption while using this remote processor.
In the specific case of the SDM630/660 family, this was necessary in
order to correctly bring up the clocks required by the Venus subsystem
without using particular hacks in the clock drivers.
This patch series achieves functional video encoding and decoding on
the SDM630/660 family of SoCs.
The testing was done with the following methodology:
- Boot the system (libc with GNOME DE on Wayland)
- Upload a 720p mp4 h264 sample video file [1] on the device
- Open gnome-terminal and use FFMPEG to transcode:
1. Software H264 decoder to Venus HW encoder (wow it's so fast!)
2. Venus HW decoder to Software H264 decoder
- Download the resulting files on a PC and start playback
- Playing back both files works
This patch series has been tested against the following devices:
- Sony Xperia XA2 Ultra (SDM630 Nile Discovery)
- Sony Xperia 10 (SDM630 Ganges Kirin)
[1] https://dvdloc8.com/clip.php?movieid=12167&clipid=1
AngeloGioacchino Del Regno (3):
media: venus: pm_helper: Commonize v3/v4 pmdomains and clocks
management
media: venus: core: Add sdm660 DT compatible and resource struct
media: dt-bindings: media: venus: Add sdm660 DT schema
.../bindings/media/qcom,sdm660-venus.yaml | 153 +++++
drivers/media/platform/qcom/venus/core.c | 68 +++
.../media/platform/qcom/venus/pm_helpers.c | 525 +++++++++---------
3 files changed, 498 insertions(+), 248 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm660-venus.yaml
--
2.28.0
next reply other threads:[~2020-09-26 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 12:54 kholk11 [this message]
2020-09-26 12:54 ` [PATCH 1/3] media: venus: pm_helper: Commonize v3/v4 pmdomains and clocks management kholk11
2020-09-26 16:16 ` kernel test robot
2020-09-26 16:16 ` kernel test robot
2020-09-26 12:54 ` [PATCH 2/3] media: venus: core: Add sdm660 DT compatible and resource struct kholk11
2020-09-26 12:54 ` [PATCH 3/3] media: dt-bindings: media: venus: Add sdm660 DT schema kholk11
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=20200926125412.13024-1-kholk11@gmail.com \
--to=kholk11@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marijns95@gmail.com \
--cc=martin.botka1@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=stanimir.varbanov@linaro.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 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.