From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Tue, 02 Jul 2013 19:21:52 +0200 [thread overview]
Message-ID: <87vc4sho7j.fsf@natisbad.org> (raw)
In-Reply-To: 20130702124639.GI19937@titan.lakedaemon.net
Hi,
Jason Cooper <jason@lakedaemon•net> writes:
>> - G762 PWM fan controller on I2C bus: it requires G762 driver which
>> is *currently sitting in hwmon maintainer tree* and will be available
>> in 3.11. Jason, as a side note I have a short patch for available for
>> ReadyNAS Duo v2 .dts file (the device also has a G762). I can hold
>> it until rc cycle if you prefer.
>
> Nope, post patches when you have them ready. I am capable of holding
> them until -rc1 drops ;-)
That's the one I sent yesterday (the patch tagged RESEND, i.e. w/o the
fixes for space issue in .dts file)
>> Jason, the tests were done against your for-next branch (with all the
>> fixes which accumulated in Linux tree from rc7). I will work directly
>> against Linus tree as soon as the rc- cycle for 3.11 starts.
>
> hmmm, my latest for-next (20130623) is based against v3.10-rc7, are you
> using that?
Yes, but with just your tree I got some freezes during boot and applying
the additional commits available in Linux tree, this fixed the issue. I
did not spend much the time but I think this is related to
PJ4B_ERRATA_4742 which you do not have in your for-next branch:
commit 3e0a07f8c401bb43e0f964c5f1285b2cb2028645
Author: Gregory CLEMENT <gregory.clement@free-electrons•com>
Date: Sun Jun 23 10:17:11 2013 +0100
ARM: 7773/1: PJ4B: Add support for errata 4742
This commit fixes the regression on Armada 370 (the kernal hang during
boot) introduced by the commit: "ARM: 7691/1: mm: kill unused
TLB_CAN_READ_FROM_L1_CACHE and use ALT_SMP instead".
...
>> [snip]
>>
>> +
>> + /* Waiting for NAND support to appear in armada-370.dtsi
>
> I would just leave this out until we get the driver sorted.
ok, will do that in next versions.
>> + i2c at 11000 {
>> + compatible = "marvell,mv64xxx-i2c";
>> + clock-frequency = <100000>;
>> + status = "okay";
>> +
>> + isl12057: isl12057 at 68 {
>> + compatible = "isil,isl12057";
>> + reg = <0x68>;
>> + wakeup-source;
>> + };
My main question is for ISL12057 RTC chip: I guess it's just pointless to
push the .dts file for the RN102 w/o a working RTC clock?
Cheers,
a+
next prev parent reply other threads:[~2013-07-02 17:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 20:59 [RFC] Add .dts file for Netgear ReadyNAS 102 Arnaud Ebalard
2013-07-02 12:46 ` Jason Cooper
2013-07-02 13:14 ` Thomas Petazzoni
2013-07-02 13:33 ` Jason Cooper
2013-07-02 13:38 ` Thomas Petazzoni
2013-07-02 13:44 ` Jason Cooper
2013-07-02 13:49 ` Willy Tarreau
2013-07-02 14:24 ` Jason Cooper
2013-07-02 17:22 ` Arnaud Ebalard
2013-07-02 17:41 ` Jason Cooper
2013-07-02 21:48 ` Arnaud Ebalard
[not found] ` <20130702220936.GC10215@1wt.eu>
2013-07-02 23:23 ` Ezequiel Garcia
2013-07-03 4:33 ` Willy Tarreau
2013-07-03 22:33 ` Ezequiel Garcia
2013-07-03 22:38 ` Willy Tarreau
2013-07-03 7:42 ` Thomas Petazzoni
2013-07-03 13:00 ` Ezequiel Garcia
2013-07-03 19:07 ` Willy Tarreau
2013-07-03 19:10 ` Jason Cooper
2013-07-03 19:38 ` Willy Tarreau
2013-07-03 19:39 ` Jason Cooper
2013-07-04 13:59 ` Thomas Petazzoni
2013-07-04 14:01 ` Willy Tarreau
2013-07-04 17:33 ` Jason Cooper
2013-07-03 20:21 ` Jason Cooper
2013-07-03 20:35 ` Willy Tarreau
2013-07-03 20:44 ` Jason Cooper
2013-07-03 21:14 ` Willy Tarreau
2013-07-03 22:23 ` Willy Tarreau
2013-07-03 22:58 ` Arnaud Ebalard
2013-07-04 6:15 ` Willy Tarreau
2013-07-03 21:05 ` Arnaud Ebalard
2013-07-02 17:21 ` Arnaud Ebalard [this message]
2013-07-02 17:38 ` Jason Cooper
2013-07-02 13:48 ` Sebastian Hesselbarth
2013-07-02 23:27 ` 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=87vc4sho7j.fsf@natisbad.org \
--to=arno@natisbad$(echo .)org \
--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