Hi,
On 2019-07-29 15:16, Stanimir Varbanov wrote:
Hi,
On 7/22/19 12:07 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket
Hi Stan,
On 2019-07-29 17:08, Stanimir Varbanov wrote:
Hi,
On 7/22/19 12:07 PM, Aniket Masule wrote:
Introduced clock scaling using bitrate, preavious
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This helps
Hi Stan,
On 2019-07-29 14:05, Stanimir Varbanov wrote:
Hi Aniket,
On 7/22/19 12:07 PM, Aniket Masule wrote:
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock
On 2019-07-15 21:30, Stanimir Varbanov wrote:
Hi,
On 7/2/19 5:46 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket Masule
---
Hi,
On 2019-07-15 21:28, Stanimir Varbanov wrote:
Hi,
On 7/2/19 5:46 PM, Aniket Masule wrote:
Introduced clock scaling using bitrate, preavious
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This helps in
Hi Stan,
On 2019-07-01 21:15, Stanimir Varbanov wrote:
Hi Aniket,
On 6/26/19 11:23 AM, Aniket Masule wrote:
Introduced clock scaling using bitrate, current
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This
Hi Stan,
On 2019-07-01 19:28, Stanimir Varbanov wrote:
Hi,
On 6/25/19 7:27 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket
Hi Stan,
On 2019-07-01 18:41, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock required.
Hi Stan,
On 2019-07-01 17:13, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Add vpp cycles for for different types of codec
It indicates the cycles required by video hardware
to process each macroblock. Initialize the codec
data with core resources.
Signed-off-by: Aniket
On 2019-06-17 14:37, Stanimir Varbanov wrote:
Hi Aniket,
On 6/11/19 9:05 AM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket
Hi Stan,
On 2019-06-17 14:28, Stanimir Varbanov wrote:
Hi Aniket,
On 6/11/19 9:05 AM, Aniket Masule wrote:
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock required.
Hi Stan,
On 2019-06-17 14:07, Stanimir Varbanov wrote:
Hi Aniket,
On 6/11/19 9:05 AM, Aniket Masule wrote:
Initialize the codec data with core resources.
Please squash this patch in 1/5 patch.
Yes Stan.
Signed-off-by: Aniket Masule
---
drivers/media/platform/qcom/venus/helpers.c | 30
Hi Stan,
On 2019-06-17 14:07, Stanimir Varbanov wrote:
Hi Aniket,
On 6/11/19 9:05 AM, Aniket Masule wrote:
Add vpp cycles for for different types of codec
It indicates the cycles required by video hardware
to process each macroblock.
Signed-off-by: Aniket Masule
---
13 matches
Mail list logo
