linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>,
	linux-omap@vger.kernel.org, Letux-kernel@openphoenux.org
Subject: Re: OMAP4/5 AESS on v6.4
Date: Fri, 26 May 2023 08:09:17 +0300	[thread overview]
Message-ID: <20230526050917.GB14287@atomide.com> (raw)
In-Reply-To: <85922330-D19F-474A-9F23-F12CCAC68491@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [230525 08:34]:
> > Am 25.05.2023 um 06:53 schrieb Tony Lindgren <tony@atomide.com>:
> > 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

  reply	other threads:[~2023-05-26  5:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 15:21 OMAP4/5 AESS on v6.4 H. Nikolaus Schaller
2023-05-25  4:53 ` Tony Lindgren
2023-05-25  8:32   ` H. Nikolaus Schaller
2023-05-26  5:09     ` Tony Lindgren [this message]
2023-05-26  6:21       ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230526050917.GB14287@atomide.com \
    --to=tony@atomide.com \
    --cc=Letux-kernel@openphoenux.org \
    --cc=hns@goldelico.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).