Hi Devarsh, On Thu, Feb 08, 2024 at 06:26:17PM +0530, Devarsh Thakkar wrote: > Hi Maxime, > > Thanks a lot for checking on this. > > On 26/01/24 17:45, Maxime Ripard wrote: > > Hi, > > > > Thanks a lot for working on that. > > > > On Tue, Jan 16, 2024 at 07:11:41PM +0530, Devarsh Thakkar wrote: > >> Display subsystem present in TI Keystone family of devices supports sharing > >> of display between multiple hosts as it provides separate register space > >> (common* region) for each host to programming display controller and also a > >> unique interrupt line for each host. > >> > >> This adds support for display sharing, by allowing partitioning of > >> resources either at video port level or at video plane level as > >> described below : > >> > >> 1) Linux can own (i.e have write access) completely one or more of video > >> ports along with corresponding resources (viz. overlay managers, > >> video planes) used by Linux in context of those video ports. > >> Even if Linux is owning > >> these video ports it can still share this video port with a remote core > >> which can own one or more video planes associated with this video port. > >> > >> 2) Linux owns one or more of the video planes with video port > >> (along with corresponding overlay manager) associated with these planes > >> being owned and controlled by a remote core. Linux still has read-only > >> access to the associated video port and overlay managers so that it can > >> parse the settings made by remote core. > > > > So, just to make sure we're on the same page. 1) means Linux drives the > > whole display engine, but can lend planes to the R5? How does that work, > > is Linux aware of the workload being there (plane size, format, etc) ? > > > > Well, there is no dynamic procedure being followed for lending. The > partitioning scheme is decided and known before hand, and the remote > core firmware updated and compiled accordingly, and similarly the > device-tree overlay for Linux is also updated with partitioning > information before bootup. > > What would happen here is that Linux will know before-hand this > partitioning information via device-tree properties and won't enumerate > the plane owned by RTOS, but it will enumerate the rest of the display > components and initialize the DSS, after which user can load the DSS > firmware on remote core and this firmware will only have control of > plane as it was compiled with that configuration. Right. If the RTOS is in control of a single plane, how it is expected to deal with Linux shutting the CRTC down, or enforcing a configuration that isn't compatible with what the RTOS expects (like a plane with a higher zpos masking its plane), what is the mechanism to reconcile it? > > And 2) would mean that the display engine is under the R5 control and > > Linux only gets to fill the plane and let the firmware know of what it > > wants? > > > > Here too the partitioning information is pre-decided and remote core > firmware and device-tree overlay for Linux updated accordingly. But in > this case as remote core firmware owns the display (minus the plane > owned by Linux) it is started and initialized during the bootloader > phase itself where it initializes the DSS and starts rendering using the > plane owned by it and Linux just latches to the DSS without > re-initializing it, with write access only to the plane that is owned by > Linux. You can refer [1] for more details on this. > > > If so, do we even need the tidss driver in the second case? We could > > just write a fwkms driver of some sorts that could be used by multiple > > implementations of the same "defer to firmware" logic. > > > > This feature of static partitioning of DSS resources is specific to DSS7 > hardware (which is controlled by tidss driver) which supports dedicated > register space and interrupt line for each of the hosts [0], so that > multiple hosts can drive the display controller simultaneously as per > the desired static partitioning of resources, and so I don't think a > separate driver is required here and tidss seems the right place to > support this, where using this device-tree approach different resource > partitioning schemas can be achieved as described here [1]. This was > also aligned with Tomi too where we discussed that tidss is the right > place to support this as we are simply leveraging the DSS hardware > capabilities of static partitioning here. If the only thing tidss does in the "owned by RTOS" is forwarding KMS atomic states to the RTOS, then I'm still not sure why we need to involve tidss at all. It's not just about interrupts, it's also about how your arbitrate between what Linux wants and what the RTOS wants. Like if the RTOS still wants to output something but Linux wants to disable it, how do you reconcile the two? You have to have something that reconciles both, and typically for firmware-based setup this will be the firmware's job. That's very similar to what the RaspberryPi did with fkms, and I believe that having a generic KMS-on-remoteproc driver when the firmware has control over the display is the path forward. > >> For both the cases, the resources used in context of processing core > >> running Linux along with ownership information are exposed by user as > >> part of device-tree blob and driver uses an updated feature list tailored > >> for this shared mode accordingly. The driver also auto-populates > >> matching overlay managers and output types from shared video > >> port list provided in device-tree blob. > >> In dispc_feature struct remove const access specfier for output_type > >> array as it is required to be updated dynamically in run-time for shared > >> mode. > > > > I'm also not entirely sure that the device tree is the right path there. > > Surely the firmware capabilities will evolve over time, while the device > > tree won't. Is there some way to make it discoverable at probe time by > > the driver? > > I think the main highlight of the sharing feature is the hardware > capability where each host is provided separate irq and register space > to program display for their display context independently Wait, what do you mean by display context here? Maxime
Attachment:
signature.asc
Description: PGP signature
