From: Simon Guinot <simon@sequanux.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [lm-sensors] [PATCH 1/2] hwmon: add generic GPIO fan driver
Date: Tue, 19 Oct 2010 11:46:36 +0000 [thread overview]
Message-ID: <20101019114636.GF29120@kw.sim.vm.gnt> (raw)
In-Reply-To: <20101018205034.GA10473@ericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 2125 bytes --]
Hi Guenter,
On Mon, Oct 18, 2010 at 01:50:34PM -0700, Guenter Roeck wrote:
> On Mon, Oct 18, 2010 at 04:36:10PM -0400, Simon Guinot wrote:
> [ ... ]
>
> > > I don't really understand the value of supporting pwm attributes,
> > > since you have to convert those to rpm anyway. Why not just stick
> > > with fan1_input and fan1_target ? This would simplify the code a lot.
> >
> > I don't know very well the hwmon API. I have simply been fooled by the
> > sysfs-interface document which claim that fan[1-*]_target only make
> > sense for a closed-loop fan. Moreover, I was expecting gpio-fan to be
> > compliant with the fancontrol shell script...
> >
> > But anyway, you are right. I just don't want the pwm interface.
> >
> If the fancontrol script doesn't support fanX_target, and a given fan
> doesn't support pwm, it might make sense to update it.
>
> Jean, any comments ?
>
> > > > +
> > > > +err_free_gpio:
> > > > + for (i = i - 1; i >= 0; i--)
> > > > + gpio_free(ctrl[i]);
> > > > +
> > > This misses the most recently allocated gpio pin if gpio_direction_output() failed.
> >
> > The gpio is freed above while handling the gpio_direction_output() error.
> >
> I missed that. Thatks for the clarification.
>
> > > > +
> > > > + dev_info(&pdev->dev, "GPIO fan initialized\n");
> > > > +
> > > Might be a good idea to add a notion of which fan was initialized.
> > > After all, there could be more than one.
> >
> > dev_info() don't do it for me ? anyway, I will check this too.
> >
> It probably does. Wonder what it actually shows. Can you check ?
If CONFIG_PRINTK is enabled, dev_info() end up in a dev_printk() call
with the level argument set to KERN_INFO.
The message format is:
${driver_name} ${device_name}: ${message}
Note that the device id number is part of the device name. So, if two
gpio-fan devices are initialized, you will see:
gpio-fan gpio-fan.0: GPIO fan initialized
gpio-fan gpio-fan.1: GPIO fan initialized
For a single fan device, you will see:
gpio-fan gpio-fan: GPIO fan initialized
Simon
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: simon@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] hwmon: add generic GPIO fan driver
Date: Tue, 19 Oct 2010 11:46:36 +0000 [thread overview]
Message-ID: <20101019114636.GF29120@kw.sim.vm.gnt> (raw)
In-Reply-To: <20101018205034.GA10473@ericsson.com>
Hi Guenter,
On Mon, Oct 18, 2010 at 01:50:34PM -0700, Guenter Roeck wrote:
> On Mon, Oct 18, 2010 at 04:36:10PM -0400, Simon Guinot wrote:
> [ ... ]
>
> > > I don't really understand the value of supporting pwm attributes,
> > > since you have to convert those to rpm anyway. Why not just stick
> > > with fan1_input and fan1_target ? This would simplify the code a lot.
> >
> > I don't know very well the hwmon API. I have simply been fooled by the
> > sysfs-interface document which claim that fan[1-*]_target only make
> > sense for a closed-loop fan. Moreover, I was expecting gpio-fan to be
> > compliant with the fancontrol shell script...
> >
> > But anyway, you are right. I just don't want the pwm interface.
> >
> If the fancontrol script doesn't support fanX_target, and a given fan
> doesn't support pwm, it might make sense to update it.
>
> Jean, any comments ?
>
> > > > +
> > > > +err_free_gpio:
> > > > + for (i = i - 1; i >= 0; i--)
> > > > + gpio_free(ctrl[i]);
> > > > +
> > > This misses the most recently allocated gpio pin if gpio_direction_output() failed.
> >
> > The gpio is freed above while handling the gpio_direction_output() error.
> >
> I missed that. Thatks for the clarification.
>
> > > > +
> > > > + dev_info(&pdev->dev, "GPIO fan initialized\n");
> > > > +
> > > Might be a good idea to add a notion of which fan was initialized.
> > > After all, there could be more than one.
> >
> > dev_info() don't do it for me ? anyway, I will check this too.
> >
> It probably does. Wonder what it actually shows. Can you check ?
If CONFIG_PRINTK is enabled, dev_info() end up in a dev_printk() call
with the level argument set to KERN_INFO.
The message format is:
${driver_name} ${device_name}: ${message}
Note that the device id number is part of the device name. So, if two
gpio-fan devices are initialized, you will see:
gpio-fan gpio-fan.0: GPIO fan initialized
gpio-fan gpio-fan.1: GPIO fan initialized
For a single fan device, you will see:
gpio-fan gpio-fan: GPIO fan initialized
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101019/00391386/attachment-0001.sig>
next prev parent reply other threads:[~2010-10-19 11:46 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 10:54 [lm-sensors] [PATCH 4/5] hwmon: DNS323 rev C1 fan support Benjamin Herrenschmidt
2010-05-22 10:54 ` Benjamin Herrenschmidt
2010-05-22 11:00 ` [lm-sensors] " Benjamin Herrenschmidt
2010-05-22 11:00 ` Benjamin Herrenschmidt
2010-10-13 11:59 ` [lm-sensors] " Simon Guinot
2010-10-13 11:59 ` Simon Guinot
2010-10-13 16:34 ` [lm-sensors] " Guenter Roeck
2010-10-13 16:34 ` Guenter Roeck
2010-10-17 15:40 ` Simon Guinot
2010-10-17 15:40 ` Simon Guinot
2010-10-17 15:50 ` [lm-sensors] [PATCH 1/2] hwmon: add generic GPIO fan driver Simon Guinot
2010-10-17 15:50 ` Simon Guinot
2010-10-17 15:50 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Simon Guinot
2010-10-17 15:50 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Simon Guinot
2010-10-22 1:53 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Guenter Roeck
2010-10-22 1:53 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Guenter Roeck
2010-10-22 2:08 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Nicolas Pitre
2010-10-22 2:08 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Nicolas Pitre
2010-10-22 4:30 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Guenter Roeck
2010-10-22 4:30 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Guenter Roeck
2010-10-22 9:29 ` [lm-sensors] [PATCH] [ARM] Kirkwood: add fan support for Network Simon Guinot
2010-10-22 9:29 ` [PATCH] [ARM] Kirkwood: add fan support for Network Space Max v2 Simon Guinot
2010-10-22 9:59 ` [lm-sensors] [PATCH] [ARM] Kirkwood: add fan support for Guenter Roeck
2010-10-22 9:59 ` [PATCH] [ARM] Kirkwood: add fan support for Network Space Max v2 Guenter Roeck
2010-10-22 8:27 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Simon Guinot
2010-10-22 8:27 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Simon Guinot
2010-10-22 9:58 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Guenter Roeck
2010-10-22 9:58 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Guenter Roeck
2010-10-22 18:39 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Guenter Roeck
2010-10-22 18:39 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Guenter Roeck
2010-10-22 18:50 ` [lm-sensors] [PATCH 2/2] [ARM] Kirkwood: add fan support for Nicolas Pitre
2010-10-22 18:50 ` [PATCH 2/2] [ARM] Kirkwood: add fan support for Network Space Max v2 Nicolas Pitre
2010-10-18 16:08 ` [lm-sensors] [PATCH 1/2] hwmon: add generic GPIO fan driver Guenter Roeck
2010-10-18 16:08 ` Guenter Roeck
2010-10-18 18:00 ` [lm-sensors] " Chris Moore
2010-10-18 18:00 ` Chris Moore
2010-10-18 18:35 ` [lm-sensors] " Guenter Roeck
2010-10-18 18:35 ` Guenter Roeck
2010-10-18 20:36 ` [lm-sensors] " Simon Guinot
2010-10-18 20:36 ` Simon Guinot
2010-10-18 20:50 ` [lm-sensors] " Guenter Roeck
2010-10-18 20:50 ` Guenter Roeck
2010-10-19 11:46 ` Simon Guinot [this message]
2010-10-19 11:46 ` Simon Guinot
2010-10-19 14:52 ` [lm-sensors] " Guenter Roeck
2010-10-19 14:52 ` Guenter Roeck
2010-10-19 6:52 ` [lm-sensors] " Guenter Roeck
2010-10-19 6:52 ` Guenter Roeck
2010-10-19 8:36 ` [lm-sensors] " Simon Guinot
2010-10-19 8:36 ` Simon Guinot
2010-10-19 15:15 ` [lm-sensors] " Guenter Roeck
2010-10-19 15:15 ` Guenter Roeck
2010-10-19 19:30 ` [lm-sensors] " Simon Guinot
2010-10-19 19:30 ` Simon Guinot
2010-10-21 20:07 ` [lm-sensors] " Simon Guinot
2010-10-21 20:07 ` Simon Guinot
2010-10-21 20:26 ` [lm-sensors] " Guenter Roeck
2010-10-21 20:26 ` Guenter Roeck
2010-10-19 22:03 ` [lm-sensors] " Guenter Roeck
2010-10-19 22:03 ` Guenter Roeck
2010-10-20 0:19 ` [lm-sensors] " Simon Guinot
2010-10-20 0:19 ` Simon Guinot
2010-10-20 0:50 ` [lm-sensors] " Guenter Roeck
2010-10-20 0:50 ` Guenter Roeck
2010-10-20 7:59 ` [lm-sensors] " Simon Guinot
2010-10-20 7:59 ` Simon Guinot
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=20101019114636.GF29120@kw.sim.vm.gnt \
--to=simon@sequanux.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 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.