u-boot.git/drivers/soc, branch master Unnamed repository; edit this file 'description' to name the repository. soc: ti: k3-navss-ringacc: Remove unused ring modes 2021-05-12T11:06:38+00:00 Vignesh Raghavendra vigneshr@ti.com 2021-05-10T14:36:04+00:00 f1e97c705803ab07141640238a9c3036daf03011 With AM64x supporting only K3_NAV_RINGACC_RING_MODE_RING or the exposed ring mode, all other K3 SoCs have also been moved to this common baseline. Therefore drop other modes such as K3_NAV_RINGACC_RING_MODE_MESSAGE (and proxy) to save on SPL footprint. There is a saving of ~800 bytes with this change for am65x_evm_r5_defconfig. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com> 
With AM64x supporting only K3_NAV_RINGACC_RING_MODE_RING or the exposed
ring mode, all other K3 SoCs have also been moved to this common
baseline. Therefore drop other modes such as
K3_NAV_RINGACC_RING_MODE_MESSAGE (and proxy) to save on SPL footprint.

There is a saving of ~800 bytes with this change for am65x_evm_r5_defconfig.

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
soc: ti: k3-navss-ringacc: Add AM64 ringacc support 2021-05-12T11:06:38+00:00 Vignesh Raghavendra vigneshr@ti.com 2021-05-10T14:36:03+00:00 c409b4932dba6403a706f9453d627abfb5d93e20 AM64 dual mode rings are modeled as pair of Rings objects which has common configuration and memory buffer, but separate real-time control register sets for each direction mem2dev (forward) and dev2mem (reverse). AM64 rings must be requested only using k3_ringacc_request_rings_pair(), and forward ring must always be initialized/configured. After this any other Ringacc APIs can be used without any callers changes. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> 
AM64 dual mode rings are modeled as pair of Rings objects which has common
configuration and memory buffer, but separate real-time control register
sets for each direction mem2dev (forward) and dev2mem (reverse).

AM64 rings must be requested only using k3_ringacc_request_rings_pair(),
and forward ring must always be initialized/configured. After this any
other Ringacc APIs can be used without any callers changes.

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
soc: ti: k3-socinfo: Add entry for AM64X SoC family 2021-05-12T11:02:44+00:00 Lokesh Vutla lokeshvutla@ti.com 2021-05-06T11:14:48+00:00 776b79e9f159112fca232706d4eec24275dc585c Add support for AM64 SoC identification. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> 
Add support for AM64 SoC identification.

Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
dm: treewide: Rename ..._platdata variables to just ..._plat 2020-12-13T23:51:09+00:00 Simon Glass sjg@chromium.org 2020-12-03T23:55:23+00:00 8a8d24bdf174851ebb8607f359d54b72e3283b97 Try to maintain some consistency between these variables by using _plat as a suffix for them. Signed-off-by: Simon Glass <sjg@chromium.org> 
Try to maintain some consistency between these variables by using _plat as
a suffix for them.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: treewide: Rename dev_get_platdata() to dev_get_plat() 2020-12-13T23:51:09+00:00 Simon Glass sjg@chromium.org 2020-12-03T23:55:20+00:00 c69cda25c9b59e53a6bc8969ada58942549f5b5d Rename this to be consistent with the change from 'platdata'. Signed-off-by: Simon Glass <sjg@chromium.org> 
Rename this to be consistent with the change from 'platdata'.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: treewide: Rename 'platdata' variables to just 'plat' 2020-12-13T23:51:08+00:00 Simon Glass sjg@chromium.org 2020-12-03T23:55:18+00:00 caa4daa2ae3dc0a3e516addea5772c9af76abcb0 We use 'priv' for private data but often use 'platdata' for platform data. We can't really use 'pdata' since that is ambiguous (it could mean private or platform data). Rename some of the latter variables to end with 'plat' for consistency. Signed-off-by: Simon Glass <sjg@chromium.org> 
We use 'priv' for private data but often use 'platdata' for platform data.
We can't really use 'pdata' since that is ambiguous (it could mean private
or platform data).

Rename some of the latter variables to end with 'plat' for consistency.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: treewide: Rename auto_alloc_size members to be shorter 2020-12-13T15:00:25+00:00 Simon Glass sjg@chromium.org 2020-12-03T23:55:17+00:00 41575d8e4c334df148c4cdd7c40cc825dc0fcaa1 This construct is quite long-winded. In earlier days it made some sense since auto-allocation was a strange concept. But with driver model now used pretty universally, we can shorten this to 'auto'. This reduces verbosity and makes it easier to read. Coincidentally it also ensures that every declaration is on one line, thus making dtoc's job easier. Signed-off-by: Simon Glass <sjg@chromium.org> 
This construct is quite long-winded. In earlier days it made some sense
since auto-allocation was a strange concept. But with driver model now
used pretty universally, we can shorten this to 'auto'. This reduces
verbosity and makes it easier to read.

Coincidentally it also ensures that every declaration is on one line,
thus making dtoc's job easier.

Signed-off-by: Simon Glass <sjg@chromium.org>
soc: soc_ti_k3: Add device identification for J7200 SoC 2020-08-11T15:04:46+00:00 Kishon Vijay Abraham I kishon@ti.com 2020-08-05T17:14:27+00:00 837933a620c4756cbe8035fb4bb6b25623394238 Add device identification for J7200 SoC Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by: Suman Anna <s-anna@ti.com> 
Add device identification for J7200 SoC

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
dm: soc: Introduce soc_ti_k3 driver for TI K3 SoCs 2020-07-25T20:46:57+00:00 Dave Gerlach d-gerlach@ti.com 2020-07-16T04:39:59+00:00 3e1b59cf3b425d14ebdf2fc9f07abc6874116799 Introduce an soc_ti_k3_driver that allows identification and selection of SoC specific data based on the JTAG ID register for device identification, as described for AM65x[0] and J721E[1] devices. [0] http://www.ti.com/lit/ug/spruid7e/spruid7e.pdf [1] http://www.ti.com/lit/ug/spruil1a/spruil1a.pdf Signed-off-by: Dave Gerlach <d-gerlach@ti.com> 
Introduce an soc_ti_k3_driver that allows identification and selection
of SoC specific data based on the JTAG ID register for device
identification, as described for AM65x[0] and J721E[1] devices.

[0] http://www.ti.com/lit/ug/spruid7e/spruid7e.pdf
[1] http://www.ti.com/lit/ug/spruil1a/spruil1a.pdf

Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
test: Add tests for SOC uclass 2020-07-25T20:46:57+00:00 Dave Gerlach d-gerlach@ti.com 2020-07-16T04:39:58+00:00 21e3c219aea21467766420f9d1941d12e48259bd Add a sandbox SOC driver, and some tests for the SOC uclass. Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Dave Gerlach <d-gerlach@ti.com> 
Add a sandbox SOC driver, and some tests for the SOC uclass.

Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>