From: arno@natisbad.org (Arnaud Ebalard)
To: Mark Brown <broonie@kernel.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, Mark Rutland <mark.rutland@arm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
jason@lakedaemon.net, Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-arm-kernel@lists.infradead.org,
Rob Landley <rob@landley.net>, Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Peter Huewe <peter.huewe@infineon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thierry Reding <treding@nvidia.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [rtc-linux] Re: Can someone Ack and queue a patch for RTC subsytem?
Date: Fri, 20 Dec 2013 21:23:46 +0100 [thread overview]
Message-ID: <8738lnl19p.fsf@natisbad.org> (raw)
In-Reply-To: <20131220183050.GB31886@sirena.org.uk> (Mark Brown's message of "Fri, 20 Dec 2013 18:30:50 +0000")
Hi,
Mark Brown <broonie@kernel.org> writes:
> On Thu, Dec 19, 2013 at 11:17:44PM +0100, Arnaud Ebalard wrote:
>
>> All NETGEAR ReadyNAS 102, 104 and 2120 have an ISL 12057 RTC chip which
>> is used as main RTC clock but can also provide alarm. But the alarm
>> interrupt line of the chip is *not* connected to the SoC. It is
>> connected to some power component and can be used to wake up the NAS
>> when it is completely off and the alarm rings.
>
> Can the PMIC or whatever function as an interrupt controller and report
> the interrupt on to the SoC?
I do not even know to which specific component the irq line of the chip
is connected. You can take a look at [1] to see what's on the PCB; if
you have an idea about which one could be a good candidate (TPS65251?),
I can try and check with an ohmmeter which pin is connected to confirm
your guess. Then, I could look at the datasheet (if any) to see if it
can relay the interrupt to the SoC (if the component is supported by
Linux kernel).
But, except if we can do what you propose, there are two problems at
hand:
1) I cannot currently test the IRQ handler my changes would bring
because it is not connected to the SoC on my platforms
2) even if I find a solution for 1), noone ever provided any directions
on what should be required to make some program like rtc-test.c happy on
my platforms (alarm support but no interrupt from the RTC). e.g. some
refinements like the one introduced by c9f5c7e7a84f1b7 (rtc: rtc-spear:
Provide flag for no support of UIE mode). I guess it should be fairly
simple for someone w/ good knowledge of the RTC subsystem to tell what
is needed. I do not have that knowledge and the documentation does not
help.
Regarding 1), I am starting to wonder if the best way out would not be
for me to connect the interrupt line of the ISL12057 to one of the GPIO
line currently connected to the LCD on my RN104 (after having
disconnected the LCD) and change the function of the associated MPP on
the SoC to make it an interrupt line. Could that work w/o additional
hardware modification? What are my chances of killing the board?
But this is pointless if I do not get any clear directions about 2).
Cheers,
a+
[1]: http://natisbad.org/NAS2/index.html#hw
next prev parent reply other threads:[~2013-12-20 20:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:34 Can someone Ack and queue a patch for RTC subsytem? Arnaud Ebalard
2013-12-19 16:38 ` Alessandro Zummo
2013-12-19 17:28 ` Arnaud Ebalard
2013-12-19 17:40 ` Alessandro Zummo
2013-12-19 18:01 ` Jason Cooper
2013-12-19 18:03 ` Alessandro Zummo
2013-12-19 18:05 ` Arnaud Ebalard
2013-12-19 18:09 ` Jason Cooper
2013-12-19 19:48 ` Guenter Roeck
2013-12-19 19:52 ` Jason Cooper
2013-12-19 16:46 ` Jason Cooper
2013-12-19 16:57 ` [rtc-linux] " Alessandro Zummo
2013-12-19 22:17 ` Arnaud Ebalard
2013-12-20 18:30 ` Mark Brown
2013-12-20 20:23 ` Arnaud Ebalard [this message]
2013-12-21 14:16 ` Mark Brown
2013-12-19 17:46 ` Arnaud Ebalard
2013-12-19 17:49 ` Alessandro Zummo
2013-12-20 9:03 ` Maxime Ripard
2013-12-19 17:50 ` Jason Cooper
2013-12-20 0:57 ` Jason Cooper
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=8738lnl19p.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.huewe@infineon.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sfr@canb.auug.org.au \
--cc=swarren@wwwdotorg.org \
--cc=treding@nvidia.com \
/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