Re: OMAP4/5 AESS on v6.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [230525 08:34]:
> > Am 25.05.2023 um 06:53 schrieb Tony Lindgren <tony@xxxxxxxxxxx>:
> > You could also check some driver registers for
> > context lost status in the driver as the context lost registers are outside
> > the driver IO range. And after that, using reset framework for context lost
> > status could be done, maybe by adding support to drivers/soc/ti/omap_prm.c.
> 
> Ok. I'll look into that.

So reset_control_status() could maybe return -EIO error if context was lost.
Or maybe something like reset_control_context_lost() could be implemented.
Needs to be discussed on the related mailing lists of course. Then omap_prm.c
just needs the context lost registers mapped, and consumer drivers can check
context lost status from the reset framework.

Regards,

Tony



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux