; Bryan O'Donoghue
>Subject: RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver
>
>>> +static struct soc_sensor_entry *alloc_soc_dts(void)
>>> +{
>>> + struct soc_sensor_entry *aux_entry;
>>> + int err;
>>> + u32 out;
>>>
>-Original Message-
>From: Kweh, Hock Leong
>Sent: Monday, February 23, 2015 3:39 PM
>To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com
>Cc: linux...@vger.kernel.org; LKML; Bryan O'Donoghue
>Subject: RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal dr
> -Original Message-
> From: Ong, Boon Leong
> Sent: Monday, February 23, 2015 9:39 AM
> Subject: RE: [PATCH] thermal: intel Quark SoC X1000 DTS thermal driver
>
> >Just to bring out for discussion, do you think we should put a "safety range"
> &g
>-Original Message-
>From: Bryan O'Donoghue [mailto:pure.lo...@nexus-software.ie]
>Sent: Thursday, February 12, 2015 7:37 PM
>To: Ong, Boon Leong; Zhang, Rui; edubez...@gmail.com
>Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] t
>Just to bring out for discussion, do you think we should put a "safety range"
>for reporting out the critical trip temperature value (mean the value from
>register minus 1 or 2 degree)?
>
>Just wondering if this is needed for the software to have the sufficient
>shutdown time before the HW make a
On 11/02/15 16:51, Ong Boon Leong wrote:
In Intel Quark SoC X1000, there is one on-die digital temperature sensor(DTS).
The DTS offers both hot & critical trip points.
However, in current distribution of UEFI BIOS for Quark platform, only
the current
critical trip point is configured to be 105
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Ong Boon Leong
> Sent: Thursday, February 12, 2015 12:52 AM
> To: Zhang, Rui; edubez...@gmail.com
> Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subjec
7 matches
Mail list logo
