From: Sudeep Holla <sudeep.holla@arm.com>
To: Sujeet Kumar Baranwal <sbaranwal@marvell.com>
Cc: linux-arm-kernel@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: scmi sensor
Date: Mon, 14 Oct 2019 18:08:51 +0100 [thread overview]
Message-ID: <20191014170851.GB323@bogus> (raw)
In-Reply-To: <BYAPR18MB2438D5CE74FADE66F1EEFC66AF900@BYAPR18MB2438.namprd18.prod.outlook.com>
On Mon, Oct 14, 2019 at 06:26:57AM +0000, Sujeet Kumar Baranwal wrote:
> Hi Sudeep,
>
> In order to use scmi sensor TRIP_POINT_NOTIFY part, the protocol only
> specifies trip points to be configured, and it doesn't have any handler
> associated that shall be invoked upon those points being violated on agent.
> After registering the trip points for a sensor, how does the linux scmi
> sensor driver ever comes to know any violations reported by SCP?!
The notification part is not yet implemented. It's yet another work
in progress feature.
>
> In the scmi_rx_callback() in ISR context, I only see complete(xfer->done)
> which would only let a blocked thread know it could proceed but that means
> some application needs to be initiated and permanently stalled, listening
> to this event?
>
Yes we need to set up Rx channel, buffers and then handle the event.
Rx channel support was added in v5.4, I have posted patch for setting up
buffers[1] but didn't merge without the user. I am still debating on how
to add notification APIs from SCMI for it's users.
> My requirement is that some how I register a call back in linux's scmi senor
> protocol that would be called when trip values are violated and it shall be
> initiated by platform to the agent. It doesn't appear to be a possibility
> looking at the current implementation and msg ids of scmi sensor protocol.
> Am I missing something?
>
As I mentioned earlier all these are WIP. Without platform to test, I am
not actively developing these. I can share patches when it's in good shape.
--
Regards,
Sudeep
[1] https://lore.kernel.org/lkml/20190708154730.16643-6-sudeep.holla@arm.com/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2019-10-14 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR18MB2438D5CE74FADE66F1EEFC66AF900@BYAPR18MB2438.namprd18.prod.outlook.com>
2019-10-14 17:08 ` Sudeep Holla [this message]
2019-10-14 18:57 ` [EXT] Re: scmi sensor Sujeet Kumar Baranwal
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=20191014170851.GB323@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sbaranwal@marvell.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