From: Willy Tarreau <w@1wt.eu>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: ARM: dts: rockchip: add the MiQi board's fan definition
Date: Sat, 11 Feb 2017 18:45:54 +0100 [thread overview]
Message-ID: <20170211174554.GA14513@1wt.eu> (raw)
In-Reply-To: <3614963.WjR2ddleWK@phil>
Hi Heiko,
On Sat, Feb 11, 2017 at 05:33:16PM +0100, Heiko Stuebner wrote:
> Hi Willy,
>
> Am Samstag, 11. Februar 2017, 09:56:55 CET schrieb Willy Tarreau:
> > The MiQi board is sold with an enclosure in which a fan is connected
> > to the second LED output, and configured by default in "heartbeat"
> > mode so that it rotates slowly and increases when the CPU load
> > increases, ensuring appropriate cooling by default. This LED output
> > is called "Fan" in the original kernel and connected to GPIO18
> > (gpiochip 0, pin 18). Here we called it "miqi:green:fan" to stay
> > consistent with the kernel's naming conventions.
>
> I tend to disagree with this approach. A fan is not a led and the devicetree
> is about describing the hardware, not how a specific kernel likes to use things
> :-) .
Sure but I was trying to stay as close as possible to the intended
purpose of the connector on the board as it is sold :-)
> The kernel already has a gpio-fan driver (drivers/hwmon) or you could
> resurrect the gpio-pwm patch [0] from Olliver Schinagl and use the pwm-fan on
> top of that for more intermediate steps.
Ah it's great to know there has already been something like this because
I thought about developing one for the same reason.
> > It's worth noting that without this patch the fan doesn't work at
> > all, risking to make the board overheat.
>
> At least cpufreq is already hooked to the thermal controller on the rk3288, so
> even without additional cooling it should select lower cpu frequencies keeping
> the heat in line and prevent overheating the board.
Well that's one way to see it, as for me throttling the CPU is the last
resort before seeing it die ; I find it sad to waste all the performance
of a 3288 that way, otherwise it's easier to use something like a dirt
a much slower and cheaper cortex A5. But I agree with the point regarding
the gpio-pwm. I think that mqmaker initially designed the GPIO to be used
as a led to benefit from the heartbeat trigger which more or less replaces
what a more efficient thermal control could achieve.
Thanks!
Willy
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: dts: rockchip: add the MiQi board's fan definition
Date: Sat, 11 Feb 2017 18:45:54 +0100 [thread overview]
Message-ID: <20170211174554.GA14513@1wt.eu> (raw)
In-Reply-To: <3614963.WjR2ddleWK@phil>
Hi Heiko,
On Sat, Feb 11, 2017 at 05:33:16PM +0100, Heiko Stuebner wrote:
> Hi Willy,
>
> Am Samstag, 11. Februar 2017, 09:56:55 CET schrieb Willy Tarreau:
> > The MiQi board is sold with an enclosure in which a fan is connected
> > to the second LED output, and configured by default in "heartbeat"
> > mode so that it rotates slowly and increases when the CPU load
> > increases, ensuring appropriate cooling by default. This LED output
> > is called "Fan" in the original kernel and connected to GPIO18
> > (gpiochip 0, pin 18). Here we called it "miqi:green:fan" to stay
> > consistent with the kernel's naming conventions.
>
> I tend to disagree with this approach. A fan is not a led and the devicetree
> is about describing the hardware, not how a specific kernel likes to use things
> :-) .
Sure but I was trying to stay as close as possible to the intended
purpose of the connector on the board as it is sold :-)
> The kernel already has a gpio-fan driver (drivers/hwmon) or you could
> resurrect the gpio-pwm patch [0] from Olliver Schinagl and use the pwm-fan on
> top of that for more intermediate steps.
Ah it's great to know there has already been something like this because
I thought about developing one for the same reason.
> > It's worth noting that without this patch the fan doesn't work at
> > all, risking to make the board overheat.
>
> At least cpufreq is already hooked to the thermal controller on the rk3288, so
> even without additional cooling it should select lower cpu frequencies keeping
> the heat in line and prevent overheating the board.
Well that's one way to see it, as for me throttling the CPU is the last
resort before seeing it die ; I find it sad to waste all the performance
of a 3288 that way, otherwise it's easier to use something like a dirt
a much slower and cheaper cortex A5. But I agree with the point regarding
the gpio-pwm. I think that mqmaker initially designed the GPIO to be used
as a led to benefit from the heartbeat trigger which more or less replaces
what a more efficient thermal control could achieve.
Thanks!
Willy
next prev parent reply other threads:[~2017-02-11 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 8:56 ARM: dts: rockchip: add the MiQi board's fan definition Willy Tarreau
2017-02-11 8:56 ` Willy Tarreau
[not found] ` <1486803415-14680-1-git-send-email-w-K+wRfnb2/UA@public.gmane.org>
2017-02-11 16:33 ` Heiko Stuebner
2017-02-11 16:33 ` Heiko Stuebner
2017-02-11 17:45 ` Willy Tarreau [this message]
2017-02-11 17:45 ` Willy Tarreau
[not found] ` <20170211174554.GA14513-K+wRfnb2/UA@public.gmane.org>
2017-02-12 1:41 ` Heiko Stuebner
2017-02-12 1:41 ` Heiko Stuebner
2017-02-12 7:17 ` Willy Tarreau
2017-02-12 7:17 ` Willy Tarreau
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=20170211174554.GA14513@1wt.eu \
--to=w@1wt.eu \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.