On 08-10-2013 04:45, Hongbo Zhang wrote:
> On 09/25/2013 10:15 PM, Eduardo Valentin wrote:
>> On 25-09-2013 03:13, Hongbo Zhang wrote:
>>> On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
>>> You are introducing new concept here, the
On 09/25/2013 10:15 PM, Eduardo Valentin wrote:
On 25-09-2013 03:13, Hongbo Zhang wrote:
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
cannot use this, right? any further plan to
On 09/25/2013 10:15 PM, Eduardo Valentin wrote:
On 25-09-2013 03:13, Hongbo Zhang wrote:
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
cannot use this, right? any further plan to
On 08-10-2013 04:45, Hongbo Zhang wrote:
On 09/25/2013 10:15 PM, Eduardo Valentin wrote:
On 25-09-2013 03:13, Hongbo Zhang wrote:
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
On Tue, Sep 24, 2013 at 10:33:19PM +0100, Eduardo Valentin wrote:
> On 23-09-2013 06:40, Mark Rutland wrote:
> >
> > It would be nice to have a name for the cells after a phandle which
> > describe the cooling device's configuration. You've called them
> > parameters here, but it probably makes
On Tue, Sep 24, 2013 at 10:33:19PM +0100, Eduardo Valentin wrote:
On 23-09-2013 06:40, Mark Rutland wrote:
It would be nice to have a name for the cells after a phandle which
describe the cooling device's configuration. You've called them
parameters here, but it probably makes sense to
On 25-09-2013 01:39, Hongbo Zhang wrote:
> On 09/24/2013 11:50 PM, Eduardo Valentin wrote:
>> Zhang,
>>
>> I appreciate your interest. I am replying a couple of your comments.
>> Please also check my answers to Mark's queries on other email thread.
> When I replied to Mark yesterday, I missed your
On 25-09-2013 03:13, Hongbo Zhang wrote:
> On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
>> [...]
>> +
>> +/*** sensor API ***/
>> +
>
> You are introducing new concept here, the original framework and drivers
> cannot use this, right? any further plan to update original framework
> for
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
cannot use this, right? any further plan to update original framework
for this new feature?
+static struct thermal_zone_device *
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
cannot use this, right? any further plan to update original framework
for this new feature?
+static struct thermal_zone_device *
On 25-09-2013 03:13, Hongbo Zhang wrote:
On 09/19/2013 05:35 AM, Eduardo Valentin wrote:
[...]
+
+/*** sensor API ***/
+
You are introducing new concept here, the original framework and drivers
cannot use this, right? any further plan to update original framework
for this new
On 25-09-2013 01:39, Hongbo Zhang wrote:
On 09/24/2013 11:50 PM, Eduardo Valentin wrote:
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
When I replied to Mark yesterday, I missed your mail
On 09/24/2013 11:50 PM, Eduardo Valentin wrote:
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
When I replied to Mark yesterday, I missed your mail replying him already.
I should check that mail
On 23-09-2013 06:40, Mark Rutland wrote:
>
> It would be nice to have a name for the cells after a phandle which
> describe the cooling device's configuration. You've called them
> parameters here, but it probably makes sense to call them a
> cooling-specifier (following clock-specifier and
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
On 24-09-2013 04:11, Hongbo Zhang wrote:
> On 09/23/2013 06:40 PM, Mark Rutland wrote:
>> Hi Eduardo,
>>
>> Apologies for having taken so long to get
On 09/23/2013 06:40 PM, Mark Rutland wrote:
Hi Eduardo,
Apologies for having taken so long to get back you on this.
I have several comments on the binding and the way it's parsed.
On Wed, Sep 18, 2013 at 10:35:36PM +0100, Eduardo Valentin wrote:
This patch introduces a device tree bindings
On 09/23/2013 06:40 PM, Mark Rutland wrote:
Hi Eduardo,
Apologies for having taken so long to get back you on this.
I have several comments on the binding and the way it's parsed.
On Wed, Sep 18, 2013 at 10:35:36PM +0100, Eduardo Valentin wrote:
This patch introduces a device tree bindings
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
On 24-09-2013 04:11, Hongbo Zhang wrote:
On 09/23/2013 06:40 PM, Mark Rutland wrote:
Hi Eduardo,
Apologies for having taken so long to get back
On 23-09-2013 06:40, Mark Rutland wrote:
It would be nice to have a name for the cells after a phandle which
describe the cooling device's configuration. You've called them
parameters here, but it probably makes sense to call them a
cooling-specifier (following clock-specifier and
On 09/24/2013 11:50 PM, Eduardo Valentin wrote:
Zhang,
I appreciate your interest. I am replying a couple of your comments.
Please also check my answers to Mark's queries on other email thread.
When I replied to Mark yesterday, I missed your mail replying him already.
I should check that mail
On 23-09-2013 06:40, Mark Rutland wrote:
> Hi Eduardo,
>
Hi Mark,
> Apologies for having taken so long to get back you on this.
>
Well, at least we are keeping it up somehow. I just would like to have
an agreement, at least for the binding part, as I mentioned before.
> I have several
Hi Eduardo,
Apologies for having taken so long to get back you on this.
I have several comments on the binding and the way it's parsed.
On Wed, Sep 18, 2013 at 10:35:36PM +0100, Eduardo Valentin wrote:
> This patch introduces a device tree bindings for
> describing the hardware thermal behavior
Hi Eduardo,
Apologies for having taken so long to get back you on this.
I have several comments on the binding and the way it's parsed.
On Wed, Sep 18, 2013 at 10:35:36PM +0100, Eduardo Valentin wrote:
This patch introduces a device tree bindings for
describing the hardware thermal behavior
On 23-09-2013 06:40, Mark Rutland wrote:
Hi Eduardo,
Hi Mark,
Apologies for having taken so long to get back you on this.
Well, at least we are keeping it up somehow. I just would like to have
an agreement, at least for the binding part, as I mentioned before.
I have several comments
This patch introduces a device tree bindings for
describing the hardware thermal behavior and limits.
Also a parser to read and interpret the data and feed
it in the thermal framework is presented.
This patch introduces a thermal data parser for device
tree. The parsed data is used to build
This patch introduces a device tree bindings for
describing the hardware thermal behavior and limits.
Also a parser to read and interpret the data and feed
it in the thermal framework is presented.
This patch introduces a thermal data parser for device
tree. The parsed data is used to build
26 matches
Mail list logo
