From: klightspeed@killerwolves•net (Ben Peddell)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv1 2/3] arm: mvebu: add .dts file for Synology DS213j
Date: Tue, 18 Nov 2014 08:41:27 +1000 [thread overview]
Message-ID: <546A7997.1040603@killerwolves.net> (raw)
In-Reply-To: <878ujas07o.fsf@natisbad.org>
On 17/11/14 18:25, Arnaud Ebalard wrote:
> Hi,
>
> Ben Peddell <klightspeed@killerwolves•net> writes:
>
>> On 16/11/2014 11:14 PM, Arnaud Ebalard wrote:
>>>>> + gpio-fan-100-32-35 {
>>>> There is some logic to this naming, but i don't remember what it is.
>>>> Did you check this is appropriate?
>>> The 32-35 is for the MPP i.e. fan uses mpp32 to mpp35 (3 MPP for speed,
>>> one for alarm). I don't know what the 100 part means. What I did is I
>>> googled to see which fan supported kirkwood models have and noticed
>>> that the DS212j uses the exact same fan, i.e. Y.S.Tech FD129225LL-N so
>>> I opted for the same naming.
>>>
>>> On that aspect, you may be able to explain why the speed-map for this
>>> fan goes up to 5000 RPM. This fan is supposed to operate at 1900RPM.
>>> Note that it does not matter in practice.
>>
>> On the Kirkwood Diskstations, the first number (100, 120 or 150) refers
>> to the middle of the three fan speed resistors,
>
> Would not have found that alone ;-) Thanks for clarifying.
>
>> the second number (15 or
>> 32) refers to the first fan control pin, and the third number (18 or 35)
>> refers to the first fan alarm pin.
>>
>> i.e. the 100-32-35 uses fan speed resistors of 33, 100 and 150 ohms,
>> uses pins 32-34 for fan control, and uses pin 35 for the fan alarm.
>>
>> The 5000RPM was interpolated from my measured RPM pulse rate (4200PPM)
>> of the 80mm fan in my DS211j (which uses the 150-32-35 fan config) at
>> maximum RPM.
>
> Then, I think I need to change the speed map to have 1900 RPM as max
> speed. Out of curiosity, how did you measured the RPM pulse rate
> exactly?
I hooked a logic analyzer to the sense pin and measured the pulse rate.
Looking at the specifications of the fan in this unit (an EC7025L12ER),
it has a maximum fan speed of 3000RPM, so it looks like it uses two
pulses per revolution and not one as I had assumed when I created the
speed map.
next prev parent reply other threads:[~2014-11-17 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 0:04 [PATCHv1 0/3] arm: mvebu: add Synology DS213j and DS414 .dts files Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 1/3] arm: mvebu: add uartX labels for Armada SoC serial nodes Arnaud Ebalard
2014-11-16 1:09 ` Andrew Lunn
2014-11-16 12:34 ` Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 2/3] arm: mvebu: add .dts file for Synology DS213j Arnaud Ebalard
2014-11-16 2:00 ` Andrew Lunn
2014-11-16 2:31 ` Andrew Lunn
2014-11-16 13:14 ` Arnaud Ebalard
2014-11-16 23:23 ` Ben Peddell
2014-11-17 8:25 ` Arnaud Ebalard
2014-11-17 22:41 ` Ben Peddell [this message]
2014-11-17 23:23 ` Arnaud Ebalard
2014-11-16 0:04 ` [PATCHv1 3/3] arm: mvebu: add .dts file for Synology DS414 Arnaud Ebalard
2014-11-16 2:15 ` Andrew Lunn
2014-11-16 13:17 ` Arnaud Ebalard
2014-11-16 2:20 ` [PATCHv1 0/3] arm: mvebu: add Synology DS213j and DS414 .dts files Andrew Lunn
2014-11-16 13:24 ` 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=546A7997.1040603@killerwolves.net \
--to=klightspeed@killerwolves$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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