Drivers Allwinner A83t

If the Smartphone Flash Tool didn’t detect your Oppo A83t, you might need to press the volume down or up button but do not power your phone. If you don’t install all the necessary drivers, you may experience issues detecting your phone with the PC. Download VCOM Driver Download MTK USB Driver. Allwinner Technology is a fabless semiconductor company that designs mixed-signal systems on a chip (SoC). The company is headquartered in Zhuhai, Guangdong, China.It has a sales and technical support office in Shenzhen, Guangdong, and logistics operations in Hong Kong. Since its founding in 2007, Allwinner has released over fifteen SoC processors for use in Android-based tablets, as well as. Download local driver Automatic downloads from our server. If you click over them, automatically will be downloaded a driver installer for your Android brand. To know more information about these drivers you can visit our section “Tutorials”. Green buttons Official download sites.

This page is related to the hardware, for software see:

  • Cedrus The project for a 100% libre open source driver and software.
  • CedarX Allwinner's media framework software libraries.

Video Engine is the plain name used by Allwinner for the hardware block responsible for the task of decoding and encoding video formats.

Allwinner

Naming

There is some confusion around how to name this video engine, with the principal reason been the non-existent clear branding by Allwinner.

Drivers
  • CedarX
is the name given to the proprietary software libraries for video and audio de-/encoding (CedarV + CedarA).
  • Cedar Engine
is found in the kernel driver (/dev/cedar_dev) source code where it has been directly referred to as 'cedar engine' in error/information messages and internal variables. Take note that this is the kernel driver that was made for the proprietary libraries that already existed in Melis OS, were the media player application goes by the name 'cedar'.
  • MACC - Media ACCelerate video engine
is also found in the kernel driver and respective headers, where the mmio area (registers) is referenced by macc as a prefix for the definition of the register base address.
  • VE - Video Engine
is the most common name used in all the places for this hardware block. It is believed that VE is a short form of VCE (Video Codec Engine) to be in accordance with ACE (Audio Codec Engine) and is also the best generic name to describe this type of hardware block.

Naming in the datasheets and user manuals.

A83tA83t

Drivers Allwinner A83t 8

SOC features label block diagram related registers
A10 VPU VE VE
A10s VPU VPU VE
A13 VPU VPU VE
A20 Video Engine (Phoenix 3.0) Video Engine VE
A23 Video Engine Video Engine VE
A31 Video Engine Video Engine VE
A31s Video Engine Video Engine VE
A33 Video Engine Video Engine VE
A80 Video Engine Video Engine VE
A83T Video Engine claims decoder/encoder is part of the GPU block VE
H3 Video Engine Video Engine VE
A64 Video Engine Video Engine VE

Drivers Allwinner A83t 1

Retrieved from 'http://linux-sunxi.org/index.php?title=Video_Engine&oldid=18810'

Drivers Allwinner A83t 3

None
imp
Summary

The X-Powers AC100 provides an RTC and an audio codec to at least the Banana Pi-M3 (a83t). Driver is ported from NetBSD, currently only supports the RTC bits.

Repository
rS FreeBSD src repository
Lint
Lint Skipped
Unit
Unit Tests Skipped
Build Status
Buildable 12967

Event Timeline

kevans created this revision.Nov 17 2017, 6:51 PM
Herald added subscribers: andrew, imp. · View Herald TranscriptNov 17 2017, 6:51 PM
kevans updated this revision to Diff 35386.Nov 17 2017, 7:18 PM
Comment Actions
kevans updated this revision to Diff 35388.Nov 17 2017, 7:34 PM
Comment Actions

Sorry, should be the last correction for now- simplified the ofw compat bits.

manu added inline comments.Nov 18 2017, 10:25 AM
sys/arm/allwinner/files.allwinner
15
andrew added a comment.Nov 18 2017, 5:13 PM
Comment Actions

It feels like this should be 2 drivers. One to talk with the ac100, and a second jsut for the rtc bits.

manu added a comment.Nov 18 2017, 5:24 PM
Comment Actions

It feels like this should be 2 drivers. One to talk with the ac100, and a second jsut for the rtc bits.

You never talk to the ac100, only to the rtc bits or the coded bits.
This is what DT calls MFD (Multi Function Device) and I never knew what is the best way to represent it in our drivers.

kevans updated this revision to Diff 35639.Nov 23 2017, 6:39 AM
Comment Actions

standard -> optional ac100, add ac100 to the arm/GENERIC config near rsb and axp209/axp81x.

emaste added a comment.Dec 19 2017, 2:14 PM
Comment Actions

This is what DT calls MFD (Multi Function Device) and I never knew what is the best way to represent it in our drivers.

How would an eventual codec driver interact with this one?

Herald added 1 blocking reviewer(s): manu. · View Herald TranscriptDec 19 2017, 2:14 PM
kevans added a comment.Dec 26 2017, 1:01 AM
Comment Actions

This is what DT calls MFD (Multi Function Device) and I never knew what is the best way to represent it in our drivers.

How would an eventual codec driver interact with this one?

AFAICT, it's intended that the AC100 bits should be an all-in-one kind of driver, thus the codec driver would 'attach' like the RTC does here; not actually having its own resources or anything to that effect, and sharing a context with the RTC.

linimon retitled this revision from Add ac100 driver to [new driver] allwinner/ac100: rtc and audio codec for a83t.Aug 2 2018, 10:27 PM
PathSize
325 lines
1 line
1 line
    • ·Reviewers: ARM, arm64, imp, mmel, hselasky, johalun, Core Team