Forum | Documentation | Website | Blog

Skip to content
Snippets Groups Projects
Commit 830e08cf authored by Suraj  Sonawane's avatar Suraj Sonawane
Browse files

update

parent a26b36bb
Branches
No related merge requests found
......@@ -56,10 +56,32 @@ Overview
`BeagleBone AI-64 <https://docs.beagleboard.org/latest/boards/beaglebone/ai-64/>`_, is built on a proven open source Linux approach, bringing a massive amount of computing power to the hands of developers in an easy to use single board computer. Leveraging the Texas Instruments TDA4VM SOC with dual 64-bit Arm® Cortex®-A72, C7x DSP along with deep learning, vision and multimedia accelerators, developers have access to faster analytics, more data storage options, more high speed interfaces including all the connectors you’ll need on board to build applications such as Autonomous Robotics, Vision and Video Analytics, Hi-End Drones, Media Servers, and Smart Buildings.
TI-SCI
`TI-SCI <https://docs.beagleboard.org/latest/boards/beaglebone/ai-64/>`_
--------
Texas Instruments’ System Control Interface (TISCI) defines the communication protocol between various processing entities to the System Control Entity on TI SoCs. This is a set of message formats and sequence of operations required to communicate and get system services processed from the System Control Entity in the SoC.
- Texas Instruments’ System Control Interface (TISCI) defines the communication protocol between various processing entities to the System Control Entity on TI SoCs. This is a set of message formats and sequence of operations required to communicate and get system services processed from the System Control Entity in the SoC.
- TISCI protocol is used to talk to the system software.
Drivers needed to implement TI-SCI:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Device Management: Enable and release a module
- This configures both **power and clock** details for the module and keeps track of its usage.
- Add this support driver to allow communication with system controller entity within the SoC using the mailbox client.
- Clock Management: Control the frequency of the clock to a module.
- Device Reset Control
`J721E Device ID: <https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/devices.html#soc-doc-j721e-public-devices-desc-device-list>`_
~~~~~~~~~~~~~~~~~
- The device IDs represent SoC subsystems that can be modified via DMSC TISCI message APIs.
- Some Secure, Power, and Resource Management DMSC subsystem TISCI message APIs define a device ID as a parameter allowing a user to specify management of a particular SoC subsystem.
`J721E Clock ID: <https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/clocks.html>`_
~~~~~~~~~~~~~~~~
- TISCI message Power Management APIs define a device ID and clock ID as parameters allowing a user to specify granular control of clocks for a particular SoC subsystem.
`DM Timer Controller <http://www.ti.com/lit/pdf/spruil1>`_
---------------------
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment