On Fri, Sep 23, 2011 at 11:28 AM, Paul Walmsley wrote:
> On Fri, 23 Sep 2011, J, KEERTHY wrote:
>
>> On Fri, Sep 23, 2011 at 10:48 AM, Paul Walmsley wrote:
>> > On Thu, 22 Sep 2011, Keerthy wrote:
>> >
>> >> ---
>> >> arch/arm/mach-omap2/
On Fri, Sep 23, 2011 at 10:46 AM, Paul Walmsley wrote:
> On Thu, 22 Sep 2011, Keerthy wrote:
>
>> OMAP4460 specific temperature sensor register bit fields are added.
>> Existing OMAP4 entries are renamed to OMAP4430.
>
> This patch ignores the comments posted here:
>
> http://marc.info/?l=linux-om
On Fri, Sep 23, 2011 at 10:45 AM, Paul Walmsley wrote:
> On Thu, 22 Sep 2011, Keerthy wrote:
>
>> The patch series adds support of system control module device and adds
>> support
>> temperature sensor. The patch series adds hwmod for system control module
>> and enables the clocks for temperatur
On Fri, Sep 23, 2011 at 10:48 AM, Paul Walmsley wrote:
> On Thu, 22 Sep 2011, Keerthy wrote:
>
>> div_ts_ck feeds only the temperature sensor functional clock
>> and also has a clksel associated (for divider selection). Mapping this
>> as well as the bandgap_ts_fclk the fclk of temperature sensor
=
>> --- /dev/null 1970-01-01 00:00:00.0 +
>> +++ linux-omap-2.6/Documentation/hwmon/omap_temp_sensor 2011-09-22
>> 18:57:23.180918857 +0530
>> @@ -0,0 +1,25 @@
>> +Kernel driver omap_temp_sensor
>> +===
On Tue, Sep 6, 2011 at 11:42 PM, Guenter Roeck
wrote:
> On Tue, 2011-09-06 at 14:02 -0400, J, KEERTHY wrote:
>> On Thu, Sep 1, 2011 at 10:10 AM, Guenter Roeck
>> wrote:
>> > On Thu, Sep 01, 2011 at 12:09:14AM -0400, Paul Walmsley wrote:
>> >> On W
On Thu, Sep 1, 2011 at 4:46 AM, Paul Walmsley wrote:
> Hi Keerthy, Benoît,
>
> On Wed, 31 Aug 2011, Keerthy wrote:
>
>> From: Benoit Cousson
>>
>> OMAP4460 temperature sensor hwmod cannot be auto generated
>> since it is part of ctrl module. Hence populating the
>> necessary hwmod info manually.
On Thu, Sep 1, 2011 at 10:10 AM, Guenter Roeck
wrote:
> On Thu, Sep 01, 2011 at 12:09:14AM -0400, Paul Walmsley wrote:
>> On Wed, 31 Aug 2011, Guenter Roeck wrote:
>>
>> > On Wed, Aug 31, 2011 at 08:36:43PM -0400, Paul Walmsley wrote:
>> > > Hi
>> > >
>> > > Some comments.
>> > >
>> > > On Wed, 31
On Thu, Sep 1, 2011 at 9:39 AM, Paul Walmsley wrote:
> On Wed, 31 Aug 2011, Guenter Roeck wrote:
>
>> On Wed, Aug 31, 2011 at 08:36:43PM -0400, Paul Walmsley wrote:
>> > Hi
>> >
>> > Some comments.
>> >
>> > On Wed, 31 Aug 2011, Keerthy wrote:
>> >
>> [ ... ]
>> >
>> > > +}
>> > > +
>> > > +/* Sys
e_register failed.\n");
>> + ret = PTR_ERR(temp_sensor->hwmon_dev);
>> + goto hwmon_reg_err;
>> + }
>> +
>> + mutex_lock(&temp_sensor->sensor_mutex);
>> + omap_temp_sensor_configure_thresholds_mask(temp_sensor, 1,
On Thu, Sep 1, 2011 at 5:26 AM, Paul Walmsley wrote:
> Hi,
>
> On Wed, 31 Aug 2011, Keerthy wrote:
>
>> On chip temperature sensor driver. The driver monitors the temperature of
>> the MPU subsystem of the OMAP4. It sends notifications to the user space if
>> the temperature crosses user defined t
On Thu, Sep 1, 2011 at 5:34 AM, Paul Walmsley wrote:
> On Wed, 31 Aug 2011, Keerthy wrote:
>
>> OMAP4460 specific temperature sensor register bit fields are added.
>> Existing OMAP4 entries are renamed to OMAP4430.
>>
>> Signed-off-by: Keerthy
>> Cc: t...@atomide.com
>
> At least one of these bit
On Fri, Aug 26, 2011 at 9:46 PM, Guenter Roeck
wrote:
> On Fri, 2011-08-26 at 07:17 -0400, J, KEERTHY wrote:
>> On Thu, Aug 25, 2011 at 9:26 PM, Guenter Roeck
>> wrote:
>> > On Thu, 2011-08-25 at 10:06 -0400, Guenter Roeck wrote:
>> >> On Thu, Aug 25, 2011 a
On Thu, Aug 25, 2011 at 9:26 PM, Guenter Roeck
wrote:
> On Thu, 2011-08-25 at 10:06 -0400, Guenter Roeck wrote:
>> On Thu, Aug 25, 2011 at 06:30:07AM -0400, J, KEERTHY wrote:
>> > On Wed, Aug 24, 2011 at 10:46 PM, Guenter Roeck
>> > wrote:
>> > > On Wed, Au
On Thu, Aug 25, 2011 at 9:49 PM, Guenter Roeck
wrote:
> On Thu, 2011-08-25 at 12:04 -0400, J, KEERTHY wrote:
>> On Thu, Aug 25, 2011 at 7:36 PM, Guenter Roeck
>> wrote:
>> > On Thu, Aug 25, 2011 at 06:30:07AM -0400, J, KEERTHY wrote:
>> >> On Wed, Aug
On Thu, Aug 25, 2011 at 9:26 PM, Guenter Roeck
wrote:
> On Thu, 2011-08-25 at 10:06 -0400, Guenter Roeck wrote:
>> On Thu, Aug 25, 2011 at 06:30:07AM -0400, J, KEERTHY wrote:
>> > On Wed, Aug 24, 2011 at 10:46 PM, Guenter Roeck
>> > wrote:
>> > > On Wed, Au
On Thu, Aug 25, 2011 at 7:36 PM, Guenter Roeck
wrote:
> On Thu, Aug 25, 2011 at 06:30:07AM -0400, J, KEERTHY wrote:
>> On Wed, Aug 24, 2011 at 10:46 PM, Guenter Roeck
>> wrote:
>> > On Wed, Aug 24, 2011 at 10:37:12AM -0400, Keerthy wrote:
>> >> On chip t
rnel driver omap_temp_sensor
>> +==
>> +
>> +Supported chips:
>> + * Texas Instruments OMAP4460
>> + Prefix: 'omap_temp_sensor'
>> + Datasheet: http://focus.ti.com/docs/prod/folders/print/tmp102.html
>> +
>
&g
On Thu, Aug 25, 2011 at 1:22 AM, Janakiram Sistla
wrote:
>
>
> On Wed, Aug 24, 2011 at 1:18 PM, J, KEERTHY wrote:
>>
>> On Wed, Aug 24, 2011 at 10:06 PM, Janakiram Sistla
>> wrote:
>> > Hi Keerthy,
>> >
>> > Can you please point me
map_temp_sensor
>> new file mode 100644
>> index 000..e01a6d6
>> --- /dev/null
>> +++ b/Documentation/hwmon/omap_temp_sensor
>> @@ -0,0 +1,27 @@
>> +Kernel driver omap_temp_sensor
>> +==========
>> +
>> +Supported chips:
>
On Tue, Aug 23, 2011 at 9:48 AM, Rajendra Nayak wrote:
> On 8/23/2011 5:28 AM, Kevin Hilman wrote:
>>
>> Rajendra Nayak writes:
>>
>> [...]
>>
>>> FWIK, its a one time requirement to set the clock rate to the
>>> right rate the device can operate in based on what a platform
>>> supports.
>>
>> Ex
On Fri, Aug 19, 2011 at 11:04 AM, Todd Poynor wrote:
> On Thu, Aug 18, 2011 at 04:22:15PM +0530, Keerthy wrote:
> ...
>> +static int omap_temp_sensor_clk_enable(struct omap_temp_sensor *temp_sensor)
>> +{
>> + u32 ret = 0;
>> +
>> + if (temp_sensor->clk_on) {
>> + dev_err(temp_
+++ b/drivers/hwmon/Makefile
>> @@ -91,6 +91,7 @@ obj-$(CONFIG_SENSORS_MAX6639) += max6639.o
>> obj-$(CONFIG_SENSORS_MAX6642) += max6642.o
>> obj-$(CONFIG_SENSORS_MAX6650) += max6650.o
>> obj-$(CONFIG_SENSORS_MC13783_ADC)+= mc13783-adc.o
>> +obj-$(CONFIG_SE
On Fri, Aug 19, 2011 at 11:47 AM, Guenter Roeck
wrote:
> On Fri, Aug 19, 2011 at 02:04:58AM -0400, J, KEERTHY wrote:
>> On Fri, Aug 19, 2011 at 7:43 AM, Guenter Roeck
>> wrote:
>> > On Thu, Aug 18, 2011 at 06:52:15AM -0400, Keerthy wrote:
>> >> On chip t
On Fri, Aug 19, 2011 at 11:34 AM, J, KEERTHY wrote:
> On Fri, Aug 19, 2011 at 7:43 AM, Guenter Roeck
> wrote:
>> On Thu, Aug 18, 2011 at 06:52:15AM -0400, Keerthy wrote:
>>> On chip temperature sensor driver. The driver monitors the temperature of
>>> the MPU su
On Fri, Aug 19, 2011 at 11:34 AM, J, KEERTHY wrote:
> On Fri, Aug 19, 2011 at 7:43 AM, Guenter Roeck
> wrote:
>> On Thu, Aug 18, 2011 at 06:52:15AM -0400, Keerthy wrote:
>>> On chip temperature sensor driver. The driver monitors the temperature of
>>> the MPU su
/omap_temp_sensor
>> @@ -0,0 +1,27 @@
>> +Kernel driver omap_temp_sensor
>> +==
>> +
>> +Supported chips:
>> + * Texas Instruments OMAP4460
>> + Prefix: 'omap_temp_sensor'
>> + Datasheet: http://focus.ti.co
On Wed, Aug 17, 2011 at 7:15 PM, Guenter Roeck
wrote:
> On Wed, Aug 17, 2011 at 06:37:10AM -0400, J, KEERTHY wrote:
> [ ... ]
>>
>> Hi Guenter,
>>
>> Any inputs on the driver?
>>
> Hi Keerthy.
>
> I think there was so much feedback that I would just a
On Mon, Aug 15, 2011 at 11:52 AM, J, KEERTHY wrote:
> Hi,
>
> Thanks for the Review Durga.
>
> On Wed, Aug 10, 2011 at 10:05 PM, R, Durgadoss wrote:
>> Hi,
>>
>>> -Original Message-
>>> From: lm-sensors-boun...@lm-sensors.org [mailto:lm-sens
t;> obj-$(CONFIG_SENSORS_PCF8591) += pcf8591.o
>> diff --git a/drivers/hwmon/omap_temp_sensor.c
>> b/drivers/hwmon/omap_temp_sensor.c
>> new file mode 100644
>> index 000..15e2559
>> --- /dev/null
>> +++ b/drivers/hwmon/omap_temp_sensor.c
>> @@ -0,0
On Fri, Aug 12, 2011 at 3:07 AM, Roger Quadros wrote:
> On 08/11/2011 01:55 PM, Felipe Balbi wrote:
>> Hi,
>>
>> On Thu, Aug 11, 2011 at 09:54:09PM +0300, Felipe Balbi wrote:
> you need some other way to handle this. Why do you need to manually set
> the rate rather than having hwmod handl
On Thu, Aug 11, 2011 at 7:42 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Aug 11, 2011 at 06:30:04PM +0530, J, KEERTHY wrote:
>> >> >> diff --git a/drivers/hwmon/omap_temp_sensor.c
>> >> >> b/drivers/hwmon/omap_temp_sensor.c
>> >>
On Thu, Aug 11, 2011 at 7:35 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Aug 11, 2011 at 04:31:50PM +0530, J, KEERTHY wrote:
>> On Thu, Aug 11, 2011 at 4:00 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Thu, Aug 11, 2011 at 08:10:07AM +0530, J, KEERTHY
On Thu, Aug 11, 2011 at 4:06 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Aug 11, 2011 at 03:27:26PM +0530, J, KEERTHY wrote:
>> On Wed, Aug 10, 2011 at 6:16 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > (why aren't below in Cc ?
>>
>&g
On Thu, Aug 11, 2011 at 4:00 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Aug 11, 2011 at 08:10:07AM +0530, J, KEERTHY wrote:
>> >> diff --git a/arch/arm/plat-omap/Kconfig b/arch/arm/plat-omap/Kconfig
>> >> index 6e6735f..8fd8e80 100644
>> >> --- a/ar
NSORS_PC87360) += pc87360.o
>> obj-$(CONFIG_SENSORS_PC87427) += pc87427.o
>> obj-$(CONFIG_SENSORS_PCF8591) += pcf8591.o
>> diff --git a/drivers/hwmon/omap_temp_sensor.c
>> b/drivers/hwmon/omap_temp_sensor.c
>> new file mode 100644
>> index 000
evice.c
>> b/arch/arm/mach-omap2/temp_sensor_device.c
>> new file mode 100644
>> index 000..5d5e92f
>> --- /dev/null
>> +++ b/arch/arm/mach-omap2/temp_sensor_device.c
>> @@ -0,0 +1,85 @@
>> +/*
>> + * OMAP on die Temperature sensor device file
>> + *
>&g
data.c
>> b/arch/arm/mach-omap2/temp_sensor4460_data.c
>> new file mode 100644
>> index 000..294963d
>> --- /dev/null
>> +++ b/arch/arm/mach-omap2/temp_sensor4460_data.c
>> @@ -0,0 +1,63 @@
>> +/*
>> + * OMAP4460 on die Temperature sensor data file
&
On Thu, Jul 21, 2011 at 8:56 PM, J, KEERTHY wrote:
> On Thu, Jul 7, 2011 at 2:59 PM, Paul Walmsley wrote:
>> Hi
>>
>> On Tue, 5 Jul 2011, Vishwanath BS wrote:
>>
>>> From: Keerthy
>>>
>>> Patch adds hwmod entry for 4460 thermal sensor modul
On Thu, Jul 7, 2011 at 2:59 PM, Paul Walmsley wrote:
> Hi
>
> On Tue, 5 Jul 2011, Vishwanath BS wrote:
>
>> From: Keerthy
>>
>> Patch adds hwmod entry for 4460 thermal sensor module. Thermal sensor module
>> is part of Control module sharing its address space and clocked via Bandgap
>> Functional
he same author:
>
> $ git grep -e MODULE_AUTHOR drivers/mfd/twl4030-madc.c
> drivers/hwmon/twl4030-madc-hwmon.c
> drivers/hwmon/twl4030-madc-hwmon.c:MODULE_AUTHOR("J Keerthy");
> drivers/mfd/twl4030-madc.c:MODULE_AUTHOR("J Keerthy");
>
> but added on differen
Hi Sanjeev,
Thanks. Changes look good to me.
On Mon, Jul 11, 2011 at 8:50 PM, Sanjeev Premi wrote:
> A mutex is locked on entry into twl4030_madc_conversion().
> Immediate return on some error conditions leaves the
> mutex locked.
>
> This patch ensures that mutex is always unlocked before
> lea
On Wed, May 4, 2011 at 9:41 AM, Steve Sakoman wrote:
> On Tue, May 3, 2011 at 12:49 PM, J, KEERTHY wrote:
>> Hello Steve,
>>
>> Can you try adding this patch?
>
> Thanks!
>
> I tried the patch and it did indeed fix the issue. We should try to
> get this in m
Hello Steve,
Can you try adding this patch?
Regards,
Keerthy
On Tue, May 3, 2011 at 8:44 PM, Steve Sakoman wrote:
> On Wed, Mar 2, 2011 at 2:15 AM, Samuel Ortiz wrote:
>> Hi Keerthy,
>>
>> On Tue, Mar 01, 2011 at 07:12:06PM +0530, Keerthy wrote:
>>> MADC(Monitoring ADC) driver enables monitori
Hello All,
I am writing a driver for OMAP4460 thermal sensor. I have a requirement
to send events to the user space from the driver on some condition.
I am using kobject_uevent(&temp_sensor->dev->kobj, KOBJ_ADD) as
part of initialization.
On the occurrence of the event i am notifying via
kobject
Hello All,
I am trying to implement a driver for the OMAP temperature sensor.
It is an on chip sensor.
The sensor is responsible for reporting the temperature. The sensor
has configurable thresholds. The user can configure the thresholds.
An interrupt will be generated as soon as there the temper
Hello All,
Any comments on this patch?
Regards,
Keerthy
On Wed, Mar 2, 2011 at 2:17 AM, Keerthy wrote:
> twl4030_wdt driver and omap_wdt driver are registering as misc_device name as
> "watchdog" and the same minor number WATCHDOG_MINOR( value = 130).
> There is a conflict since the name and mi
On Mon, Feb 28, 2011 at 6:30 AM, Samuel Ortiz wrote:
> Hi Keerthy,
>
> On Thu, Feb 24, 2011 at 08:48:33PM +0530, Keerthy wrote:
>> Introducing a driver for MADC on TWL4030 powerIC. MADC stands for monitoring
>> ADC. This driver monitors the real time conversion of analog signals like
>> battery te
On Mon, Feb 28, 2011 at 9:11 AM, Guenter Roeck
wrote:
> On Sun, Feb 27, 2011 at 08:03:07PM -0500, Samuel Ortiz wrote:
>> Hi Keerthy,
>>
>> On Thu, Feb 24, 2011 at 08:48:50PM +0530, Keerthy wrote:
>> > This driver exposes the sysfs nodes of the TWL4030 MADC module.
>> > All the voltage channel valu
t; +/*
> + *
> + * TWL4030 MADC module driver-This driver monitors the real time
> + * conversion of analog signals like battery temperature,
> + * battery type, battery level etc.
> + *
> + * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
> + * J Keerthy
On Fri, Feb 18, 2011 at 5:38 AM, Tony Lindgren wrote:
> * Keerthy [110215 20:53]:
>> From: Richard woodruff
>>
>> This errata occurs when the ARDY interrupt generation is enabled.
>> At the begining of every new transaction the ARDY interrupt is cleared.
>>
>> On continuous i2c transactions wher
Documentation/hwmon/twl4030-madc-hwmon
>> new file mode 100644
>> index 000..2cf1cc2
>> --- /dev/null
>> +++ b/Documentation/hwmon/twl4030-madc-hwmon
>> @@ -0,0 +1,45 @@
>> +Kernel driver twl4030-madc
>> +=
>> +
>> +Su
Hello all,
I will resend once again the right set. I apologise.
Regards,
Keerthy
On Wed, Feb 16, 2011 at 5:56 PM, Keerthy wrote:
> MADC(Monitoring ADC) driver enables monitoring analog signals using
> analog-to-digital conversion (ADC) on the input source.
> The previous discussion concluded in
On Wed, Feb 16, 2011 at 5:22 AM, Ben Dooks wrote:
> On Tue, Feb 15, 2011 at 10:13:58AM +0530, J, KEERTHY wrote:
>> On Tue, Feb 15, 2011 at 5:35 AM, Kevin Hilman wrote:
>> > Keerthy writes:
>> >
>> >> From: Richard woodruff
>> >>
>>
On Tue, Feb 15, 2011 at 5:35 AM, Kevin Hilman wrote:
> Keerthy writes:
>
>> From: Richard woodruff
>>
>> ProDB00017052 - ARDY interrupt reasserted after being cleared.
>
>> This errata caused intermittent i2c instabilty(1 error per 3 hours) on
>> several
>> customer platforms. After applying th
On Fri, Feb 11, 2011 at 4:20 PM, Jarkko Nikula wrote:
> On Fri, 11 Feb 2011 12:15:18 +0530
> Keerthy wrote:
>
>> From: Richard woodruff
>>
>> ProDB00017052 - ARDY interrupt reasserted after being cleared.
>> This errata caused intermittent i2c instabilty(1 error per 3 hours) on
>> several
>> cu
Mayuresh,
Now i can see Linux-Omap on http://git.kernel.org/
Regards,
Keerthy
On Thu, Feb 10, 2011 at 1:27 PM, Menon, Nishanth wrote:
> On Thu, Feb 10, 2011 at 13:18, Janorkar, Mayuresh wrote:
>> Thanks Keerthy that link is working fine.
>>
>> My concern was that on git.kernel.org (Main Page)
Mayuresh,
Can you try this link:
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
Regards,
Keerthy
On Thu, Feb 10, 2011 at 11:57 AM, Janorkar, Mayuresh wrote:
> Hi!
>
> I am not able to find linux-omap tree on git.kernel.org.
> But linux-omap-pm is present.
>
> Something migh
On Fri, Jan 7, 2011 at 5:42 PM, J, KEERTHY wrote:
> On Fri, Jan 7, 2011 at 3:25 AM, Guenter Roeck
> wrote:
>> On Thu, 2011-01-06 at 15:21 -0500, Mark Brown wrote:
>>> On Thu, Jan 06, 2011 at 07:04:30AM -0800, Guenter Roeck wrote:
>>> > On Thu, Jan 06, 2011 at 0
On Fri, Jan 7, 2011 at 3:25 AM, Guenter Roeck
wrote:
> On Thu, 2011-01-06 at 15:21 -0500, Mark Brown wrote:
>> On Thu, Jan 06, 2011 at 07:04:30AM -0800, Guenter Roeck wrote:
>> > On Thu, Jan 06, 2011 at 07:07:13AM -0500, Mark Brown wrote:
>>
>> > > Why? It's not like hwmon has an unreasonably lar
On Fri, Jan 7, 2011 at 4:14 PM, Mark Brown
wrote:
> On Fri, Jan 07, 2011 at 02:55:45PM +0530, J, KEERTHY wrote:
>> On Thu, Jan 6, 2011 at 5:34 PM, Mark Brown
>> > On Thu, Jan 06, 2011 at 09:26:40AM +0530, Keerthy wrote:
>
>> >> +static ssi
xed to particular inputs? The temperatures should be temp_
> and if the inputs are from known sources it'd be good to label them.
Yes some are voltages and some are fixed to particular inputs.
I will label them.
>
>> + madc->imr = (pdata->irq_line == 1) ?
>> +
twl4030-madc.o
>> obj-$(CONFIG_SENSORS_VIA_CPUTEMP)+= via-cputemp.o
>> obj-$(CONFIG_SENSORS_VIA686A) += via686a.o
>> obj-$(CONFIG_SENSORS_VT1211) += vt1211.o
>> diff --git a/drivers/hwmon/twl4030-madc.c b/drivers/hwmon/twl4030-madc.c
>> new file mode 100644
>&g
e battery temperature,
> + * battery type, battery level etc. User can also ask for the conversion on a
> + * particular channel using the sysfs nodes.
> + *
> + * Copyright (C) 2010 Texas Instruments Incorporated - http://www.ti.com/
> + * J Keerthy
> + *
> + * Based on twl4030-
ONFIG_SENSORS_VIA686A) += via686a.o
>> obj-$(CONFIG_SENSORS_VT1211) += vt1211.o
>> diff --git a/drivers/hwmon/twl4030-madc.c b/drivers/hwmon/twl4030-madc.c
>> new file mode 100644
>> index 000..42f7d4a
>> --- /dev/null
>> +++ b/drivers/hwmon/twl4030-madc.c
Hello Anand,
-Original Message-
From: Gadiyar, Anand
Sent: Tuesday, November 09, 2010 7:10 PM
To: J, KEERTHY; lm-sens...@lm-sensors.org; guenter.ro...@ericsson.com;
sa...@linux.intel.com; kh...@linux-fr.org
Cc: mikko.k.yli...@nokia.com; Balbi, Felipe; amit.kuche...@canonical.com;
linux
> -Original Message-
> From: Guenter Roeck [mailto:guenter.ro...@ericsson.com]
> Sent: Thursday, September 16, 2010 8:48 PM
> To: J, KEERTHY
> Cc: linux-omap@vger.kernel.org; lm-sens...@lm-sensors.org; Krishnamoorthy,
> Balaji T
> Subject: Re: [lm-sensors] [PATC
> -Original Message-
> From: Guenter Roeck [mailto:guenter.ro...@ericsson.com]
> Sent: Thursday, September 16, 2010 7:36 PM
> To: J, KEERTHY
> Cc: linux-omap@vger.kernel.org; lm-sens...@lm-sensors.org; Krishnamoorthy,
> Balaji T
> Subject: Re: [lm-sensors] [PA
101 - 168 of 168 matches
Mail list logo
