common: cmd_dump: Gracefully handle ti_sci_cmd_get_clk_state() failure
If one has a kernel with configs like this:
CONFIG_DEVMEM=y
CONFIG_GENERIC_LIB_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
CONFIG_IO_STRICT_DEVMEM=y
then mmap'ing /dev/mem will fail. This results in all sort of issues,
but eventually will lead to a segfault if invoked like so on the
j784s4-evm:
[root@fedora build]# k3conf dump clock 218
Map fail
Map fail
Map fail
k3_sec_proxy_send: Thread23 verification failed. ret = -2
|-----------------------------------------------------------------------|
| VERSION INFO |
|-----------------------------------------------------------------------|
| K3CONF | (version v0.3-4-g16ee9a4 built Tue Mar 05 15:48:09 UTC 2024) |
| SoC | J784S4 SR1.0 |
|-----------------------------------------------------------------------|
Map fail
Map fail
Map fail
k3_sec_proxy_send: Thread23 verification failed. ret = -2
Segmentation fault (core dumped)
[root@fedora build]#
Let's at least avoid the segfault by not using the NULL pointer returned
by ti_sci_cmd_get_clk_state().
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
If one has a kernel with configs like this:
CONFIG_DEVMEM=y
CONFIG_GENERIC_LIB_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
CONFIG_IO_STRICT_DEVMEM=y
then mmap'ing /dev/mem will fail. This results in all sort of issues,
but eventually will lead to a segfault if invoked like so on the
j784s4-evm:
[root@fedora build]# k3conf dump clock 218
Map fail
Map fail
Map fail
k3_sec_proxy_send: Thread23 verification failed. ret = -2
|-----------------------------------------------------------------------|
| VERSION INFO |
|-----------------------------------------------------------------------|
| K3CONF | (version v0.3-4-g16ee9a4 built Tue Mar 05 15:48:09 UTC 2024) |
| SoC | J784S4 SR1.0 |
|-----------------------------------------------------------------------|
Map fail
Map fail
Map fail
k3_sec_proxy_send: Thread23 verification failed. ret = -2
Segmentation fault (core dumped)
[root@fedora build]#
Let's at least avoid the segfault by not using the NULL pointer returned
by ti_sci_cmd_get_clk_state().
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
readme: Add disclaimer about /dev/mem usage
Users may want to know up front that this tool needs access to /dev/mem,
in particular to talk over the mailboxes. Without this users may face
errors.
This includes making sure CONFIG_DEVMEM_STRICT_IO is disabled, as most
systems will actively be using the mailboxes necessary to communicate.
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
Users may want to know up front that this tool needs access to /dev/mem,
in particular to talk over the mailboxes. Without this users may face
errors.
This includes making sure CONFIG_DEVMEM_STRICT_IO is disabled, as most
systems will actively be using the mailboxes necessary to communicate.
Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
soc: Add support for J722S
Add SoC data and initial support for J722S device
family.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Add SoC data and initial support for J722S device
family.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
common: Fix 32-bit print & scan issues
The code doesn't work on 32-bit builds as the printf & scanf formats
used are not correct. Fix these by using the formatting macros.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Reviewed-by: Andrew Davis <afd@ti.com>
The code doesn't work on 32-bit builds as the printf & scanf formats
used are not correct. Fix these by using the formatting macros.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Cmake: Add an option to build static executable
Add an option in cmake for generating static executable.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
Add an option in cmake for generating static executable.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
readme: markdown formatting clean up
Update the README file with markdown formatting clean ups.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
Update the README file with markdown formatting clean ups.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
CMakeLists.txt: Bump to 0.3
Major changes in the release:
- New supported SoCs
- Am62x, AM62Ax, AM62Px
- J721S2/AM68, J784S4/AM69
- New features added
- Switch over to cmake
- (experimental) DDRBW for AM62x, J721E, J7200
- Set clock parent option
- Add a proper LICENSE file
- Upgrades and Bug fixes:
- Tons of refactor of code
- Fixes across processor name, register read/write for 32bit regs
- Bunch of cosmetic fixups
Signed-off-by: Nishanth Menon <nm@ti.com>
Major changes in the release:
- New supported SoCs
- Am62x, AM62Ax, AM62Px
- J721S2/AM68, J784S4/AM69
- New features added
- Switch over to cmake
- (experimental) DDRBW for AM62x, J721E, J7200
- Set clock parent option
- Add a proper LICENSE file
- Upgrades and Bug fixes:
- Tons of refactor of code
- Fixes across processor name, register read/write for 32bit regs
- Bunch of cosmetic fixups
Signed-off-by: Nishanth Menon <nm@ti.com>
readme: add am62px to supported devices
k3conf has support for the am62px family of SoCs now. Update the readme
to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
k3conf has support for the am62px family of SoCs now. Update the readme
to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add secure proxy descriptions
Provide the secure proxy and communication path descriptions that are
allowed for the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the secure proxy and communication path descriptions that are
allowed for the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add resource assignment descriptions
The resource type IDs represent the resource ranges that are assignable
to the AM62Px's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
The resource type IDs represent the resource ranges that are assignable
to the AM62Px's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add processors information
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the AM62Px
Provide the Processor IDs available in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the AM62Px
Provide the Processor IDs available in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add host description information
These Host IDs represent processing entities for the AM62Px. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could represent a virtual machine.
Provide the Host IDs permitted in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
These Host IDs represent processing entities for the AM62Px. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could represent a virtual machine.
Provide the Host IDs permitted in the AM62Px SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add device description information
The Device IDs represent the SoC subsystems that can be modified by the
TISCI message API. Some subsystems also use a Device ID as a parameter,
allowing us to specify the management of a particular SoC subsystem.
Provide the Device IDs permitted in the AM62Px SoC family.
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Device IDs represent the SoC subsystems that can be modified by the
TISCI message API. Some subsystems also use a Device ID as a parameter,
allowing us to specify the management of a particular SoC subsystem.
Provide the Device IDs permitted in the AM62Px SoC family.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62px: add clock identifiers information
The TISCI power management API uses Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem.
Define the Clock IDs that identify the incoming and outgoing clock
signals for subsystems in the AM62Px family of SoCs
Signed-off-by: Bryan Brattlof <bb@ti.com>
The TISCI power management API uses Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem.
Define the Clock IDs that identify the incoming and outgoing clock
signals for subsystems in the AM62Px family of SoCs
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: socinfo: add am62p device identification
Add the initial information needed to properly identify an am62p SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
Add the initial information needed to properly identify an am62p SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: k3conf: Do not call soc_init() if only help is requested
The help info does not depend on the SoC. To prevent extra output
due to failing to open the SoC on PC, move this to before soc_init().
Signed-off-by: Andrew Davis <afd@ti.com>
The help info does not depend on the SoC. To prevent extra output
due to failing to open the SoC on PC, move this to before soc_init().
Signed-off-by: Andrew Davis <afd@ti.com>
common: k3conf: Do not print version in the help command
The user did not ask for the version and printing this confuses tools
like help2man which expect only help information here.
Signed-off-by: Andrew Davis <afd@ti.com>
The user did not ask for the version and printing this confuses tools
like help2man which expect only help information here.
Signed-off-by: Andrew Davis <afd@ti.com>
common: help: Remove leading newline and tabs escape sequences
These can make it harder to see what the output will look like from
only looking at the code. They also confuse tools like codespell.
Move leading newlines to a new line. Replace tab escape sequences
with real tabs.
Should result in no functional change to the help output.
Signed-off-by: Andrew Davis <afd@ti.com>
These can make it harder to see what the output will look like from
only looking at the code. They also confuse tools like codespell.
Move leading newlines to a new line. Replace tab escape sequences
with real tabs.
Should result in no functional change to the help output.
Signed-off-by: Andrew Davis <afd@ti.com>
soc: j7200: Add DDR bandwidth data
Add j7200 SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Add j7200 SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
soc: j721e: Add DDR bandwidth data
Add J721e SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Add J721e SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
soc: am62x: Add DDR bandwidth data
Add AM62x SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Add AM62x SoC DDR perf data
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
cmd: Add DDR bandwidth consumption measurement
Use DDR performance counters to measure read/write bandwidth using k3conf.
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Use DDR performance counters to measure read/write bandwidth using k3conf.
Signed-off-by: Aarya Chaumal <a-chaumal@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
common: mmio: warn invalid access once
There is no need to spam users with the same message multiple times. So
just warn the user once even though the flow occurs multiple times.
Signed-off-by: Nishanth Menon <nm@ti.com>
There is no need to spam users with the same message multiple times. So
just warn the user once even though the flow occurs multiple times.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: autoadjust_table: Drop unused variable
Use scan-build to catch unused variable
Reported-by: Andrew Davis <afd@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Use scan-build to catch unused variable
Reported-by: Andrew Davis <afd@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
tisci: Fix set parent_clock API
There was a typo in the `ti_sci_msg_set_clock_parent_req` data structure
that resulted in `set parent_clock` command not working. Fixing it
by adding the missing entry.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
There was a typo in the `ti_sci_msg_set_clock_parent_req` data structure
that resulted in `set parent_clock` command not working. Fixing it
by adding the missing entry.
Signed-off-by: Vishal Mahaveer <vishalm@ti.com>
CMakeLists.txt: Add -Wpedantic
Add pedantic warnings to the list of warnings we don't like.
Signed-off-by: Nishanth Menon <nm@ti.com>
Add pedantic warnings to the list of warnings we don't like.
Signed-off-by: Nishanth Menon <nm@ti.com>
CMakeLists.txt: Add EoL to generated files
Add end of line to generated files
Signed-off-by: Nishanth Menon <nm@ti.com>
Add end of line to generated files
Signed-off-by: Nishanth Menon <nm@ti.com>
soc: Make sure all files have end of line
Find files with 'pcregrep -LMr '\n\Z' .' and fix them.
Signed-off-by: Nishanth Menon <nm@ti.com>
Find files with 'pcregrep -LMr '\n\Z' .' and fix them.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: mmio: Print hint for non-priviledged users
Give a hint that users need sudo to be able to access /dev/mem
Signed-off-by: Nishanth Menon <nm@ti.com>
Give a hint that users need sudo to be able to access /dev/mem
Signed-off-by: Nishanth Menon <nm@ti.com>
common: k3conf: Allow register read/write even if no silicon detect
Allow register read write to occur even if the processor is not
appropriately detected.
Signed-off-by: Nishanth Menon <nm@ti.com>
Allow register read write to occur even if the processor is not
appropriately detected.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: k3conf: Enable help and version information for all users
Even on invalid silicon or even if we aren't able to get to /dev/mem, we
should still be able to provide as much help information as possible to
users.
Signed-off-by: Nishanth Menon <nm@ti.com>
Even on invalid silicon or even if we aren't able to get to /dev/mem, we
should still be able to provide as much help information as possible to
users.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: k3conf: Refactor to remove redundant else
Each of if condition exits the flow cleanly, so the arg handling could
be just clean set of if conditions.
Signed-off-by: Nishanth Menon <nm@ti.com>
Each of if condition exits the flow cleanly, so the arg handling could
be just clean set of if conditions.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: k3conf: Print only relevant version information
Without soc_info being available, it is not possible to print complete
SoC information and TISCI information, so use a global flag to indicate
complete information being available and use that to selectively print
the information available.
Signed-off-by: Nishanth Menon <nm@ti.com>
Without soc_info being available, it is not possible to print complete
SoC information and TISCI information, so use a global flag to indicate
complete information being available and use that to selectively print
the information available.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: k3conf: Use snprintf to concat strings
Use snprintf rather than strncpy+strncat.
Signed-off-by: Nishanth Menon <nm@ti.com>
Use snprintf rather than strncpy+strncat.
Signed-off-by: Nishanth Menon <nm@ti.com>
include: sec_proxy.h: Complete k3_sec_proxy_init prototype
Explicitly call out no params for k3_sec_proxy_init function prototype.
Signed-off-by: Nishanth Menon <nm@ti.com>
Explicitly call out no params for k3_sec_proxy_init function prototype.
Signed-off-by: Nishanth Menon <nm@ti.com>
common: Fix memory leak in autoadjust_table_generic_fprint()
The memory in line is not freed in one of the return paths, fix this here.
Found using Clang Static Analyzer.
Signed-off-by: Andrew Davis <afd@ti.com>
The memory in line is not freed in one of the return paths, fix this here.
Found using Clang Static Analyzer.
Signed-off-by: Andrew Davis <afd@ti.com>
cmd: read/write: Check return value of num_read_bits sscanf
Check that sscanf() succeeded and exit with help if not. Found
with Clang Static Analyzer.
Signed-off-by: Andrew Davis <afd@ti.com>
Check that sscanf() succeeded and exit with help if not. Found
with Clang Static Analyzer.
Signed-off-by: Andrew Davis <afd@ti.com>
Add LICENSE file
This is good practice and helps Debian package tools automatically
label the packages with the right license.
Signed-off-by: Andrew Davis <afd@ti.com>
This is good practice and helps Debian package tools automatically
label the packages with the right license.
Signed-off-by: Andrew Davis <afd@ti.com>
Add CMake build support
Helps with our multi-distro story, makes the Debian and OE builds easier.
The old Makefile has non-standard cross-compilation assumptions. CMake
handles this is a standard way. It also makes our install target, clean
target, handles pretty printing with optional verbosity, and much more all
using the expected standards[0].
Add CMake support and remove the old Makefile to avoid confusion.
[0] https://cmake.org/cmake/help/book/mastering-cmake/chapter/Why%20CMake.html
Signed-off-by: Andrew Davis <afd@ti.com>
Helps with our multi-distro story, makes the Debian and OE builds easier.
The old Makefile has non-standard cross-compilation assumptions. CMake
handles this is a standard way. It also makes our install target, clean
target, handles pretty printing with optional verbosity, and much more all
using the expected standards[0].
Add CMake support and remove the old Makefile to avoid confusion.
[0] https://cmake.org/cmake/help/book/mastering-cmake/chapter/Why%20CMake.html
Signed-off-by: Andrew Davis <afd@ti.com>
common: socinfo: Remove soc and rev from k3conf_soc_info
This are not used outside of socinfo.c and can be made local.
We also move soc_revision_j721e and soc_revision_generic for the same
reasons.
Functions soc_is_j721e() and soc_is_am654() are not used and by removing
them we can make soc and rev local to the soc_init() function.
Signed-off-by: Andrew Davis <afd@ti.com>
This are not used outside of socinfo.c and can be made local.
We also move soc_revision_j721e and soc_revision_generic for the same
reasons.
Functions soc_is_j721e() and soc_is_am654() are not used and by removing
them we can make soc and rev local to the soc_init() function.
Signed-off-by: Andrew Davis <afd@ti.com>
common: socinfo: Remove soc_full_name and strncat usage
Usage of strncat here causes warnings due to the possibility of not
having space for the null terminator when the string is the full
length of the destination buffer.
Simply remove the use of strncat and the need for a sized buffer
by directly assigning the const strings to a pointer and using
that in the table.
Signed-off-by: Andrew Davis <afd@ti.com>
Usage of strncat here causes warnings due to the possibility of not
having space for the null terminator when the string is the full
length of the destination buffer.
Simply remove the use of strncat and the need for a sized buffer
by directly assigning the const strings to a pointer and using
that in the table.
Signed-off-by: Andrew Davis <afd@ti.com>
common: socinfo: Do not accept REV_PG_MAX as valid revision
This revisions are zero-indexed, and REV_PG_MAX is the entry one
after the last valid entry. Do not accept REV_PG_MAX as valid.
This means we also do not need to define that value in the table.
While here remove hard-coded limits on this string size, let
the compiler size them based on the strings themselves in memory.
Signed-off-by: Andrew Davis <afd@ti.com>
This revisions are zero-indexed, and REV_PG_MAX is the entry one
after the last valid entry. Do not accept REV_PG_MAX as valid.
This means we also do not need to define that value in the table.
While here remove hard-coded limits on this string size, let
the compiler size them based on the strings themselves in memory.
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Add install and uninstall targets
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Do not assume our cross compile target
If one is using a cross compile then they should set CROSS_COMPILE.
Having a default breaks native builds like done in Debian.
Signed-off-by: Andrew Davis <afd@ti.com>
If one is using a cross compile then they should set CROSS_COMPILE.
Having a default breaks native builds like done in Debian.
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Make dynamic linking the default
Needing static linking is rare, it should not be the default. As it
may still be useful for some, allow it set during build with a flag
STATIC_BUILD=1. Add this to LDFLAGS as only the linker uses that.
Signed-off-by: Andrew Davis <afd@ti.com>
Needing static linking is rare, it should not be the default. As it
may still be useful for some, allow it set during build with a flag
STATIC_BUILD=1. Add this to LDFLAGS as only the linker uses that.
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Do not use LDFLAGS when not linking
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Do not link against librt
Most of librt has been merged with the standard lib, this
linking is not needed now.
Signed-off-by: Andrew Davis <afd@ti.com>
Most of librt has been merged with the standard lib, this
linking is not needed now.
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Remove unused DESTDIR variable
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Add phony targets at target definition
This helps make it easier to see which targets are phony and
also helps us not forget any, like we did with all and clean.
Signed-off-by: Andrew Davis <afd@ti.com>
This helps make it easier to see which targets are phony and
also helps us not forget any, like we did with all and clean.
Signed-off-by: Andrew Davis <afd@ti.com>
makefile: Allow version to work with lightweight tags
Currently only annotated tags are checked, leading to us still reporting
v0.1 while we have v0.2 tagged. Fix this here.
Signed-off-by: Andrew Davis <afd@ti.com>
Currently only annotated tags are checked, leading to us still reporting
v0.1 while we have v0.2 tagged. Fix this here.
Signed-off-by: Andrew Davis <afd@ti.com>
soc: j721e: Fix the k3conf silicon revision misprint
For J721E PG1.1 k3conf reports the silicon revision as 2.0 instead of
1.1. This is because the k3conf code assumes the silicon revisions are
1.0, 2.0 for every platform.
Fixed this by creating a separate list of silicon revisions for J721E and
other platforms.
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
For J721E PG1.1 k3conf reports the silicon revision as 2.0 instead of
1.1. This is because the k3conf code assumes the silicon revisions are
1.0, 2.0 for every platform.
Fixed this by creating a separate list of silicon revisions for J721E and
other platforms.
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
cmd: read/write: Fix the kernel crash issue on reading 32bit registers
k3conf read command leads to kernel crash on reading few 32bit registers.
This is because it always reads 64 bits at the specified register address
irrespective of the register width. For example, on j721e "k3conf read
0x43000050" leads to kernel crash because the k3conf tool tries to read 64
bits but the register width is 32 bits and the address of the next valid
register is at 0x43000060 due to which 0x43000054 - 0x43000059 addresses
are invalid which leads to kernel crash.
Inorder to fix the issue an optional argument named size is added to both
the k3conf read and write commands. The user can specify the number of
bits to be read or written in the size argument. For example,
"k3conf read 0x43000050 32", "k3conf write 0x43000050 0x10 32".
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
k3conf read command leads to kernel crash on reading few 32bit registers.
This is because it always reads 64 bits at the specified register address
irrespective of the register width. For example, on j721e "k3conf read
0x43000050" leads to kernel crash because the k3conf tool tries to read 64
bits but the register width is 32 bits and the address of the next valid
register is at 0x43000060 due to which 0x43000054 - 0x43000059 addresses
are invalid which leads to kernel crash.
Inorder to fix the issue an optional argument named size is added to both
the k3conf read and write commands. The user can specify the number of
bits to be read or written in the size argument. For example,
"k3conf read 0x43000050 32", "k3conf write 0x43000050 0x10 32".
Signed-off-by: Thejasvi Konduru <t-konduru@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
readme: add am62ax to supported devices
k3conf has support for the am62ax family of SoCs now. Update the readme
to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
k3conf has support for the am62ax family of SoCs now. Update the readme
to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add secure proxy descriptions
Provide the secure proxy and communication path descriptions that are
allowed for the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the secure proxy and communication path descriptions that are
allowed for the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add resource addignment descriptions
The resource type IDs represent the resource ranges that are assignable
to the AM62Ax's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
The resource type IDs represent the resource ranges that are assignable
to the AM62Ax's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add processors information
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the Am62Ax
Provide the Processor IDs available in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the Am62Ax
Provide the Processor IDs available in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add host description information
These Host IDs represent processing entities for the AM62Ax. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could represent a virtual machine.
Provide the Host IDs permitted in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
These Host IDs represent processing entities for the AM62Ax. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could represent a virtual machine.
Provide the Host IDs permitted in the AM62Ax SoC family
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add device description information
The Device IDs represent the SoC subsystems that can be modified by the
DMSC TISCI message APIs. Some subsystems also use a Device ID as a
parameter, allowing us to specify the management of a particular SoC
subsystem.
Provide the Device IDs permitted in the AM62Ax SoC family.
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Device IDs represent the SoC subsystems that can be modified by the
DMSC TISCI message APIs. Some subsystems also use a Device ID as a
parameter, allowing us to specify the management of a particular SoC
subsystem.
Provide the Device IDs permitted in the AM62Ax SoC family.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62ax: add clock identifiers information
The TISCI power management APIs use Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a particular
subsystem.
Define the Clock IDs that identify the incoming and outgoing clock
signals for subsystems in the AM62Ax family of SoCs
Signed-off-by: Bryan Brattlof <bb@ti.com>
The TISCI power management APIs use Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a particular
subsystem.
Define the Clock IDs that identify the incoming and outgoing clock
signals for subsystems in the AM62Ax family of SoCs
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: socinfo: add am62a device identification
Add the initial information needed to properly identify an am62a SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
Add the initial information needed to properly identify an am62a SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
readme: add j784s4 to supported devices
k3conf now has support for the j784s4. Update readme to reflect this
Signed-off-by: Bryan Brattlof <bb@ti.com>
k3conf now has support for the j784s4. Update readme to reflect this
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add secure proxy descriptions
Provide the secure proxy and communication path descriptions that are
allowed for the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the secure proxy and communication path descriptions that are
allowed for the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add resource assignment descriptions
The resource type IDs represent the resource ranges that are assignable
to the J784S4's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
The resource type IDs represent the resource ranges that are assignable
to the J784S4's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add processor information
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the J784S4
Provide the processor IDs available in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Processor IDs (not to be confused with Host IDs) represent the
*actual* physical processors in the J784S4
Provide the processor IDs available in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add host description information
These Host IDs represent processing entities for the J784S4. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could even be a virtual machine
Provide the Host IDs that are permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
These Host IDs represent processing entities for the J784S4. Typically a
host is defined as a 'processing entity' which may be an actual
processor or could even be a virtual machine
Provide the Host IDs that are permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add device description information
The Device IDs represent SoC subsystems that can be modified via the
DMSC TISCI message APIs. Some subsystems define a Device ID as a
parameter, allowing us to specify the management of a particular
SoC subsystem
Provide the Device IDs that are permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Device IDs represent SoC subsystems that can be modified via the
DMSC TISCI message APIs. Some subsystems define a Device ID as a
parameter, allowing us to specify the management of a particular
SoC subsystem
Provide the Device IDs that are permitted in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j784s4: add clock identifiers information
TISCI power management APIs define Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem
Provide the information for the Clock IDs that identify incoming and
outgoing clock signals for subsystems in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
TISCI power management APIs define Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem
Provide the information for the Clock IDs that identify incoming and
outgoing clock signals for subsystems in the J784S4
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: socinfo: add j784s4 device identification
Add the initial identification support for the j784s4 SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
Add the initial identification support for the j784s4 SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
tisci: increase size of ti_sci_processors_info
Some of the processor names for the j784s4 exceed the length we are
currently allocating inside the ti_sci_processors_info structure.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Some of the processor names for the j784s4 exceed the length we are
currently allocating inside the ti_sci_processors_info structure.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add updates for v08.04.01 sysfw
Update the tisci data corresponding to the v08.04.01 sysfw
for the j721s2
Signed-off-by: Bryan Brattlof <bb@ti.com>
Update the tisci data corresponding to the v08.04.01 sysfw
for the j721s2
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721e: add updates for v08.04.01 sysfw
Update the tisci data corresponding to the v08.04.01 sysfw
for the j721e
Signed-off-by: Bryan Brattlof <bb@ti.com>
Update the tisci data corresponding to the v08.04.01 sysfw
for the j721e
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j7200: add updates for v08.04.01 sysfw
Update the tisci data corresponding to the v08.04.01 sysfw
for the j7200
Signed-off-by: Bryan Brattlof <bb@ti.com>
Update the tisci data corresponding to the v08.04.01 sysfw
for the j7200
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: remove array indexing from soc data
When new features are added to the tisci they typically will be placed
inside the reserved spaces in the abi. This has the side effect of
reordering large portions of our data in k3conf when everything below
the additions are shifted to make room.
To make updates to the tisci easier to diff in the future, remove the
array indexing from all tisci soc data in k3conf.
There are no functional changes with this patch.
This patch was the output of:
$ find soc/ -iname '*.c' -exec sed -i 's/\[[0-9]\+\] = //g' {} \;
Signed-off-by: Bryan Brattlof <bb@ti.com>
When new features are added to the tisci they typically will be placed
inside the reserved spaces in the abi. This has the side effect of
reordering large portions of our data in k3conf when everything below
the additions are shifted to make room.
To make updates to the tisci easier to diff in the future, remove the
array indexing from all tisci soc data in k3conf.
There are no functional changes with this patch.
This patch was the output of:
$ find soc/ -iname '*.c' -exec sed -i 's/\[[0-9]\+\] = //g' {} \;
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: cmd_set: Add a set parent for clocks option
Lets add an option to setup the clock mux parent option
Signed-off-by: Nishanth Menon <nm@ti.com>
Lets add an option to setup the clock mux parent option
Signed-off-by: Nishanth Menon <nm@ti.com>
common: cmd_dump: Add an option to dump the clock mux option
Lets add a command parent_clock to be able to print the clock mux
options and the mux option that is actually selected. This depends a bit
on the clock name itself, unfortunately.
Example output:
```
|--------------------------------------------------------------------------------------|
| Clock information |
|--------------------------------------------------------------------------------------|
| Device ID | Clock ID | Clock Name | Status | Clock Frequency |
|--------------------------------------------------------------------------------------|
| 157 | 70 | DEV_BOARD0_MCU_OBSCLK0_IN | CLK_STATE_READY | 12500000 |
|--------------------------------------------------------------------------------------|
|--------------------------------------------------------------------------------------------------------------------|
| Clock Parent information |
|--------------------------------------------------------------------------------------------------------------------|
| Selected | Clock ID | Clock Name | Status | Clock Frequency |
|--------------------------------------------------------------------------------------------------------------------|
| ==> | 71 | DEV_BOARD0_MCU_OBSCLK0_IN_PARENT_MCU_OBSCLK_DIV_OUT0 | CLK_STATE_READY | 12500000 |
| | 72 | DEV_BOARD0_MCU_OBSCLK0_IN_PARENT_GLUELOGIC_HFOSC0_CLKOUT | CLK_STATE_READY | 25000000 |
|--------------------------------------------------------------------------------------------------------------------|
```
Signed-off-by: Nishanth Menon <nm@ti.com>
Lets add a command parent_clock to be able to print the clock mux
options and the mux option that is actually selected. This depends a bit
on the clock name itself, unfortunately.
Example output:
```
|--------------------------------------------------------------------------------------|
| Clock information |
|--------------------------------------------------------------------------------------|
| Device ID | Clock ID | Clock Name | Status | Clock Frequency |
|--------------------------------------------------------------------------------------|
| 157 | 70 | DEV_BOARD0_MCU_OBSCLK0_IN | CLK_STATE_READY | 12500000 |
|--------------------------------------------------------------------------------------|
|--------------------------------------------------------------------------------------------------------------------|
| Clock Parent information |
|--------------------------------------------------------------------------------------------------------------------|
| Selected | Clock ID | Clock Name | Status | Clock Frequency |
|--------------------------------------------------------------------------------------------------------------------|
| ==> | 71 | DEV_BOARD0_MCU_OBSCLK0_IN_PARENT_MCU_OBSCLK_DIV_OUT0 | CLK_STATE_READY | 12500000 |
| | 72 | DEV_BOARD0_MCU_OBSCLK0_IN_PARENT_GLUELOGIC_HFOSC0_CLKOUT | CLK_STATE_READY | 25000000 |
|--------------------------------------------------------------------------------------------------------------------|
```
Signed-off-by: Nishanth Menon <nm@ti.com>
basic clock parent api
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
soc: j721s2: set processor information
While the processor information for J721S2 is already populated, it is
not set in sci_info. As a result, "k3conf dump processors" does not show
anything. Set processors_info and num_processors to correctly dump all
processors.
Fixes: 2434dcb ("soc: j721s2 add processor information")
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Signed-off-by: Bryan Brattlof <bb@ti.com>
While the processor information for J721S2 is already populated, it is
not set in sci_info. As a result, "k3conf dump processors" does not show
anything. Set processors_info and num_processors to correctly dump all
processors.
Fixes: 2434dcb ("soc: j721s2 add processor information")
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Signed-off-by: Bryan Brattlof <bb@ti.com>
readme: document j721s2 support
k3conf now supports the j721s2. Update the readme to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
k3conf now supports the j721s2. Update the readme to reflect this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add secure proxy descriptions
Provide the secure proxy and communication path descriptions that are
allowed for the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the secure proxy and communication path descriptions that are
allowed for the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add resource assignment descriptions
The resource type IDs represents the resource ranges that are assignable
to the J721S2's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
The resource type IDs represents the resource ranges that are assignable
to the J721S2's processing entities.
Provide the board configuration resource assignment type IDs that are
permitted in the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2 add processor information
The Processor IDs (not to be confused with Host IDs) represent the
actual physical processors in the J721S2.
Provide the processor and host IDs available for the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Processor IDs (not to be confused with Host IDs) represent the
actual physical processors in the J721S2.
Provide the processor and host IDs available for the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add host description information
These Host IDs represent processing entities for the J721S2. Typically a
host is a 'processing entity' which may be an actual processor or even a
virtual machine.
Provide the Host IDs that are permitted in the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
These Host IDs represent processing entities for the J721S2. Typically a
host is a 'processing entity' which may be an actual processor or even a
virtual machine.
Provide the Host IDs that are permitted in the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add clock identifier information
TISCI power management APIs define Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem
Provide the information for the Clock IDs that identify incoming and
outgoing clock signals for subsystems in the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
TISCI power management APIs define Device IDs and Clock IDs as
parameters, allowing us granular control of the clocks for a
particular subsystem
Provide the information for the Clock IDs that identify incoming and
outgoing clock signals for subsystems in the J721S2
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: j721s2: add device description information
The Device IDs represent SoC subsystems that can be modified via the
DMSC TISCI message APIs. Some subsystems define a Device ID as a
parameter, allowing us to specify the management of a particular
SoC subsystem
Provide the Device IDs that are permitted in the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
The Device IDs represent SoC subsystems that can be modified via the
DMSC TISCI message APIs. Some subsystems define a Device ID as a
parameter, allowing us to specify the management of a particular
SoC subsystem
Provide the Device IDs that are permitted in the J721S2.
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: socinfo: add j721s2 device identification
Add the initial identification support for the j721s2 SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
Add the initial identification support for the j721s2 SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
tisci: expand the processor name field
Some of the processor names for the j721s2 exceed the reserved space
inside the ti_sci_processor_info structure.
Increase the allowed space to prevent build warnings or over-flowing
Signed-off-by: Bryan Brattlof <bb@ti.com>
Some of the processor names for the j721s2 exceed the reserved space
inside the ti_sci_processor_info structure.
Increase the allowed space to prevent build warnings or over-flowing
Signed-off-by: Bryan Brattlof <bb@ti.com>
readme: add am62x to supported devices
k3conf now has support for the am62x. Update the README to reflect this
Signed-off-by: Bryan Brattlof <bb@ti.com>
k3conf now has support for the am62x. Update the README to reflect this
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add secure proxy description information
Provide the information for the Secure Proxies and communication paths
that are permitted in the am62x SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the information for the Secure Proxies and communication paths
that are permitted in the am62x SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add resource assignment information
The resource type IDs represent am62x resources ranges assignable to SoC
Processing Entities
Provide the information needed for the Board Configuration resource
assignment type IDs that are permitted in the am62x SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
The resource type IDs represent am62x resources ranges assignable to SoC
Processing Entities
Provide the information needed for the Board Configuration resource
assignment type IDs that are permitted in the am62x SoC
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add processor description information
Processor IDs (not to be confused with HOST_ID) represents an actual
physical processor on the am62x
Provide the information for the Processor & Host IDs that are permitted
Signed-off-by: Bryan Brattlof <bb@ti.com>
Processor IDs (not to be confused with HOST_ID) represents an actual
physical processor on the am62x
Provide the information for the Processor & Host IDs that are permitted
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add host description information
These host IDs represent Processing Entities which is mandatory
identification of a Host in a processor
Provide the information for the Host IDs that are permitted in the am62x
Signed-off-by: Bryan Brattlof <bb@ti.com>
These host IDs represent Processing Entities which is mandatory
identification of a Host in a processor
Provide the information for the Host IDs that are permitted in the am62x
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add clock identifier information
Provide the information for the clock IDs that identify incoming and
outgoing clocks from devices identified via device IDs in am62x SoC.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Provide the information for the clock IDs that identify incoming and
outgoing clocks from devices identified via device IDs in am62x SoC.
Signed-off-by: Bryan Brattlof <bb@ti.com>
soc: am62x: add device description information
The device IDs represent SoC subsystems that can be modified via
DMSC TISCI message APIs
Provide the information for Device IDs that are permitted in the am62x
Signed-off-by: Bryan Brattlof <bb@ti.com>
The device IDs represent SoC subsystems that can be modified via
DMSC TISCI message APIs
Provide the information for Device IDs that are permitted in the am62x
Signed-off-by: Bryan Brattlof <bb@ti.com>
common: socinfo: add am62x device identification
Add initial identification support for the am62x SoC using the
CTRLMMR_WKUP_JTAGID and secure proxy registers
Signed-off-by: Bryan Brattlof <bb@ti.com>
Add initial identification support for the am62x SoC using the
CTRLMMR_WKUP_JTAGID and secure proxy registers
Signed-off-by: Bryan Brattlof <bb@ti.com>
include: remove the include/soc/ directory
commit d773d6721607c ("soc: j721e: Update to 2019.12 sysfw documentaion")
and 1cb1a8dbab5a0 ("soc: am65x: Update to 2019.12 sysfw documentaion")
moved all device specific header files to soc/ folders along with the
corresponding sources, and build flow ignores include/soc/*
So, cleanup the redundant headers.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
commit d773d6721607c ("soc: j721e: Update to 2019.12 sysfw documentaion")
and 1cb1a8dbab5a0 ("soc: am65x: Update to 2019.12 sysfw documentaion")
moved all device specific header files to soc/ folders along with the
corresponding sources, and build flow ignores include/soc/*
So, cleanup the redundant headers.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Bump up version to 0.2
Major changes in the release:
- New supported SoCs
- AM65x SR 2.0
- J7200 SR 1.0
- AM64x SR 1.0
- New features added
- Support for show and dump of Resource management.
- Support for providing custom host id for sysfw communication
-
- Upgrades and Bug fixes:
- Updated to sysfw 2020.08b data for all SoCs
- Fixed J721e C66x input clock ids
- Replaced http links with https
- Used WKUP_JTAG_ID for device identification
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Major changes in the release:
- New supported SoCs
- AM65x SR 2.0
- J7200 SR 1.0
- AM64x SR 1.0
- New features added
- Support for show and dump of Resource management.
- Support for providing custom host id for sysfw communication
-
- Upgrades and Bug fixes:
- Updated to sysfw 2020.08b data for all SoCs
- Fixed J721e C66x input clock ids
- Replaced http links with https
- Used WKUP_JTAG_ID for device identification
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Readme: Update the list of supported platforms
Support for J7200 and AM64x are added recently. Update README to reflect
the same.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Support for J7200 and AM64x are added recently. Update README to reflect
the same.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
soc: am64x: Add rm info
Add TISCI RM info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Add TISCI RM info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
soc: am64x: Add clocks info
Add TISCI Clocks info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Add TISCI Clocks info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
soc: am64x: Add devices info
Add TISCI Devices info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Add TISCI Devices info for AM64x devices. Data based on sysfw
v2020.08b. Also assign this data to sci_info based on SoC detection.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>