From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>
Cc: rkumbako@codeaurora.org, amit.kucheria@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] thermal: core: genetlink support for events/cmd/sampling
Date: Wed, 01 Jul 2020 09:41:44 -0700 [thread overview]
Message-ID: <d3d748b28e2ff540017129c1f3291fcaa68faa21.camel@linux.intel.com> (raw)
In-Reply-To: <8526622b-cb31-4d40-95b6-e209b3101563@linaro.org>
On Wed, 2020-07-01 at 18:31 +0200, Daniel Lezcano wrote:
> On 01/07/2020 17:49, Srinivas Pandruvada wrote:
> > [...]
> >
> > > Then I'd prefer we only introduce the events that are used or
> > > will be
> > > used soon, like the tz disable/enable, to avoid some potential
> > > dead
> > > code.
> > > We can easily add more events when they are needed.
> > >
> > > Srinivas, do you have plan to use the trip add/delete events?
> > Yes and also trip modify.
>
> Ok I will keep those then.
>
> > Also I need to have one more event for heartbeat like event which
> > needs
> > confirmation from user space to hardware the user process
> > controlling
> > thermal is active not dead. So whenever hardware wants to check
> > health
> > it will send an event, which user space should acknowledge
>
> Could it be the opposite? The userspace sends periodically a message
> to
> tell it is alive instead of having the kernel asking the userspace?
>
Kernel doesn't ask (there is no timer in the kernel). The HW/FW send
special event for confirmation and expects reply (This is upto the
vendors). So user space can't send randomly.
> Is it ok if we add this in a separate series ?
Yes.
Thanks,
Srinivas
>
>
>
next prev parent reply other threads:[~2020-07-01 16:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 14:45 [PATCH v2 1/5] thermal: core: Add helpers to browse the cdev, tz and governor list Daniel Lezcano
2020-06-25 14:45 ` [PATCH v2 2/5] thermal: core: Get thermal zone by id Daniel Lezcano
2020-06-30 11:54 ` Amit Kucheria
2020-06-30 15:16 ` Zhang Rui
2020-06-25 14:45 ` [PATCH v2 3/5] thermal: core: Remove old uapi generic netlink Daniel Lezcano
2020-06-30 11:47 ` Amit Kucheria
2020-07-01 9:26 ` Daniel Lezcano
2020-07-01 9:33 ` Amit Kucheria
2020-07-01 9:45 ` Daniel Lezcano
2020-07-01 12:10 ` Amit Kucheria
2020-07-01 12:13 ` Daniel Lezcano
2020-06-25 14:45 ` [PATCH v2 4/5] thermal: core: genetlink support for events/cmd/sampling Daniel Lezcano
2020-06-30 11:45 ` Amit Kucheria
2020-06-30 16:12 ` Zhang Rui
2020-06-30 18:32 ` Daniel Lezcano
2020-07-01 7:41 ` Zhang Rui
2020-07-01 8:22 ` Daniel Lezcano
2020-07-01 15:49 ` Srinivas Pandruvada
2020-07-01 16:31 ` Daniel Lezcano
2020-07-01 16:41 ` Srinivas Pandruvada [this message]
2020-06-25 14:45 ` [PATCH v2 5/5] thermal: core: Add notifications call in the framework Daniel Lezcano
2020-06-30 11:49 ` Amit Kucheria
2020-06-30 11:58 ` Daniel Lezcano
2020-06-30 11:46 ` [PATCH v2 1/5] thermal: core: Add helpers to browse the cdev, tz and governor list Amit Kucheria
2020-06-30 15:09 ` Zhang Rui
2020-06-30 18:46 ` Amit Kucheria
2020-07-01 7:08 ` Daniel Lezcano
2020-07-01 7:35 ` Daniel Lezcano
2020-07-01 7:57 ` Zhang Rui
2020-07-01 9:26 ` Amit Kucheria
2020-07-01 9:54 ` Daniel Lezcano
2020-07-01 9:50 ` Daniel Lezcano
2020-07-02 13:53 ` Zhang Rui
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=d3d748b28e2ff540017129c1f3291fcaa68faa21.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkumbako@codeaurora.org \
--cc=rui.zhang@intel.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
Powered by JetHome