From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Device tree for Atmel SAMA5D31
Date: Fri, 10 Oct 2014 09:43:14 +0800 [thread overview]
Message-ID: <543739B2.1010408@atmel.com> (raw)
In-Reply-To: <54367e8e.e5cfb40a.560f.ffffa674SMTPIN_ADDED_BROKEN@mx.google.com>
Hi Andy,
I suggest this question go to linux arm kernel mailing list.
On 10/09/2014 08:24 PM, Andy Pont wrote:
> This isn't strictly a U-Boot issue but I am hoping that there are
> appropriately knowledgeable people here who will be able to help!
>
> I am working on a Linux driver for an I2C RTC device and need to add the
> correct definitions into the device tree for the SAMA5D31 to be passed to
> the kernel at boot time. I have added:
>
> i2c0: i2c at f0014000 {
> status = "okay";
>
> rv8523c3 at 68 {
> compatible = "mc,rv8523c3";
> reg = <0x68>;
> };
> };
>
> This sets up enough to allow the basic clock functions within the RTC to
> work correctly and the hwclock command within Busybox to work correctly. I
> need to add in the definitions for a GPIO (PE31) to be used as the alarm
> interrupt pin and can't get my head around the definitions needed within the
> device tree. I have tried adding the following
>
> interrupt-parent = <&pioE>;
> interrupts = <31>;
>
> When the RTC driver is loaded by Linux the client->irq variable in the probe
> function doesn't contain a value > 0 and so doesn't setup an interrupt.
>
> Any ideas on the correct definitions needed?
Please take this file <arch/arm/boot/dts/sama5d3xdm.dtsi> as a
reference, qt1070 use GPIO PIOE 31 as interrupt. it conflict with your
setting.
> Thanks (and apologies for the noise),
>
> Andy.
Best Regards,
Bo Shen
next parent reply other threads:[~2014-10-10 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54367e8e.e5cfb40a.560f.ffffa674SMTPIN_ADDED_BROKEN@mx.google.com>
2014-10-10 1:43 ` Bo Shen [this message]
2014-10-09 12:24 [U-Boot] Device tree for Atmel SAMA5D31 Andy Pont
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=543739B2.1010408@atmel.com \
--to=voice.shen@atmel.com \
--cc=u-boot@lists.denx.de \
/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