public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv8 1/1] Add support for GMT G762/G763 PWM fan controllers
Date: Sun, 23 Jun 2013 20:07:08 +0200	[thread overview]
Message-ID: <87r4fsem5v.fsf@natisbad.org> (raw)
In-Reply-To: <20130623160659.GB17536@roeck-us.net> (Guenter Roeck's message of "Sun, 23 Jun 2013 09:06:59 -0700")

Hi,

Guenter Roeck <linux@roeck-us.net> writes:

> On Sun, Jun 23, 2013 at 05:39:32PM +0200, Simon Guinot wrote:
>> On Thu, Jun 20, 2013 at 10:21:04PM +0200, Arnaud Ebalard wrote:
>> > 
>> > GMT G762/763 fan speed PWM controller is connected directly to a fan
>> > and performs closed-loop or open-loop control of the fan speed. Two
>> > modes - PWM or DC - are supported by the chip. Introduced driver
>> > provides various knobs to control the operations of the chip (via
>> > sysfs interface). Specific characteristics of the system can be passed
>> > either using board init code or via DT. Documentation for both the
>> > driver and DT bindings are also provided.
>> > 
>> > Signed-off-by: Arnaud Ebalard <arno@natisbad.org>
>> > ---
>> > Hi Guenter,
>> > 
>> > I guess we can wait for Simon's tests against its 5Big Network to check
>> > everything is ok on another platform. Note that I also tested the patch
>> > on my (Armada 370 based) ReadyNAS 102 and it works as expected.
>> > 
>> > To be very accurate, I had to revert eda6bee6c7 to get both an out of
>> > tree driver for ISL 12057 chip and the g762 work *on the 102*, but this
>> > is an unrelated story (Debian bug #622325 [1] has more on the topic) for
>> > which I will create a separate thread. Simon, the symptom you reported
>> > for your read failures are different from those I get so I don't think
>> > the revert will fix your problem but it may be worth trying it.
>> > 
>> > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325
>> 
>> Hi Arnaud and Guenter,
>> 
>> Actually, reverting the commit eda6bee6c7 seems to solve the -ENODEV
>> issue...
>> 
> Did you let the i2c maintainers know ?

As I wrote, I will create a separate thread on the topic. It is good to
have another unrelated example for which the problem is solved by
reverting this commit. I will keep both of you in the CC: list if you
want to follow the discussion.


>> Then, I have been able to test successfully the g762 driver against the
>> following boards:
>> 
>> - 2Big NAS (open-loop mode)
>> - 2Big Network v2 (open-loop mode)
>> - 5Big Network v2 (closed-loop mode)
>> 
>> For the last, I have also been able to configure the clock frequency
>> through the platform_data structure.
>> 
>> Tested-by: Simon Guinot <simon.guinot@sequanux.org>

Thanks for your time and efforts, Simon.

Cheers,

a+

  reply	other threads:[~2013-06-23 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 20:21 [PATCHv8 1/1] Add support for GMT G762/G763 PWM fan controllers Arnaud Ebalard
2013-06-21 17:03 ` Guenter Roeck
2013-06-23 15:39 ` Simon Guinot
2013-06-23 16:06   ` Guenter Roeck
2013-06-23 18:07     ` Arnaud Ebalard [this message]
     [not found]     ` <87fvw8ehne.fsf@natisbad.org>
2013-06-24 18:30       ` [BUG] mv64xxx i2c bus lock w/ commit eda6bee6c7 Wolfram Sang
2013-06-24 21:31         ` Arnaud Ebalard
2013-06-25 21:09           ` Arnaud Ebalard

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=87r4fsem5v.fsf@natisbad.org \
    --to=arno@natisbad.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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