All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Rob Herring <robh@kernel.org>
Cc: Vinay Simha B N <simhavcs@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm dsi2hdmi bridge - temperature sensor
Date: Thu, 14 Feb 2019 20:54:54 +0100	[thread overview]
Message-ID: <20190214195454.GA3950@ravnborg.org> (raw)
In-Reply-To: <CAL_JsqJG4TPRV5bTFn2V=_vhH6b-x+ehkKgO5MuwH3cEf-poUg@mail.gmail.com>

Hi Rob.

> >
> > (Background is to not enable the display until temp is within an
> > acceptable range, and disable it if it goes out of range, to prevent
> > hw damage I guess)
> 
> The thermal framework already has support for temperature trip points
> triggering "throttlers". I guess the display could be a throttling
> device. Really, why wouldn't you just shutdown? Seems like a strange
> usecase to keep running with the display going on and off based on
> temperature.

(Jumping into the middle of a discussion here, and maybe I got it wrong)

For the devices I work with a shutdown would be highly unexpected
just because something insignificant like the display fails to work.
The devices are used to control the climate for birds, sometimes in hot areas.
We do not want the device to shut down and let emergency take over,
due to a non-functional display.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-14 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGWqDJ7Y9rxspeWBn3qky1+dqYaydu960FrFSoTpQf2-LmMjKg@mail.gmail.com>
2019-02-14 15:27 ` drm dsi2hdmi bridge - temperature sensor Rob Clark via dri-devel
2019-02-14 19:45   ` Rob Herring via dri-devel
2019-02-14 19:52     ` Vinay Simha B N via dri-devel
2019-02-14 19:54     ` Sam Ravnborg [this message]
2019-02-19 13:54       ` Vinay Simha B N

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=20190214195454.GA3950@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=simhavcs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.