Separate I3C Target from Controller logic

* Add Controller/Target support configuration options
* Separate CSR interface from the host controller
* Add a separate 'csri' module to handle the I3CCSR interface;
  Separates operations on CSRs from strictly controller-related
  module.
* Separate TTI from HCI queues tests
* Use common wrapper for the TTI/HCI queues
* Enable Target support by default
* Rework sources; separate target device from controller sources

Signed-off-by: Wiktoria Kuna <[email protected]>

Author: wkkuna

i3c_core_configs.yaml

@@ -17,6 +17,8 @@ ahb:
   FrontendBusAddrWidth: 18
   FrontendBusDataWidth: 64
   DisableInputFF: True
+  ControllerSupport: False
+  TargetSupport: True
 
 ahb_ff:
   CmdFifoDepth: 64
@@ -31,6 +33,8 @@ ahb_ff:
   FrontendBusAddrWidth: 18
   FrontendBusDataWidth: 64
   DisableInputFF: False
+  ControllerSupport: False
+  TargetSupport: True
 
 axi:
   CmdFifoDepth: 64
@@ -49,6 +53,8 @@ axi:
   FrontendBusIdFiltering: True
   NumPrivIds: 4
   DisableInputFF: True
+  ControllerSupport: False
+  TargetSupport: True
 
 axi_ff:
   CmdFifoDepth: 64
@@ -67,3 +73,5 @@ axi_ff:
   FrontendBusIdFiltering: True
   NumPrivIds: 4
   DisableInputFF: False
+  ControllerSupport: False
+  TargetSupport: True