From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Frederik Lotter
<frederik.lotter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DTB file appears to have corrupted node property according to fdtdump and kernel?
Date: Fri, 3 Feb 2017 09:56:02 +1100 [thread overview]
Message-ID: <20170202225602.GB7754@umbus.fritz.box> (raw)
In-Reply-To: <CAPBAm7QSB_-LrAwouztLYLaC0mWF2V4QQ_Yz98p6jVw07SfT6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]
On Thu, Feb 02, 2017 at 07:53:11PM +0200, Frederik Lotter wrote:
> Hi,
>
> I have a particular device tree node property which refuses to reach
> the Linux kernel without corruption:
>
> interrupts = <0xc 0x1>;
>
> >From the extract below from the preprocessed file:
>
> i2c1: i2c@f0018000 {
> compatible = "atmel,at91sam9x5-i2c";
> reg = <0xf0018000 0x4000>;
> interrupts = <0x13 0x4 0x6>;
> dmas = <0x2 0x2 0x9 0x2 0x2 0xa>;
> dma-names = "tx", "rx";
> pinctrl-names = "default";
> pinctrl-0 = <0x12>;
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> clocks = <0x13>;
> status = "okay";
> clock-frequency = <0x61a80>;
> atmel,recover-scl = <0x14 0x1b 0x0>;
> atmel,recover-sda = <0x14 0x1a 0x0>;
>
> lsm6ds3@6b {
> compatible = "st,lsm6ds3";
> reg = <0x6b>;
> pinctrl-names = "default";
> pinctrl-0 = <0x15>;
> interrupt-parent = <0x16>;
> interrupts = <0xc 0x1>;
> interrupt-names = "lsm6ds_int1";
> st,drdy-int-pin = <0x1>;
> };
> };
>
> Version: DTC 1.4.0 (ubuntu package) for manual testing.
>
> (1) fdtdump mix6000.dtb | grep interrupts
>
> Thsi returns the interrupt line as:
>
> interrupts = <0x0000000c 0x000001d0>;
>
> (2) In the linux kernel the of_platform_populate() reads the same property as:
>
> 0x0000000c 0x00000000 with lenth=8
>
> (3) If I take the DTS file and manually compile the DTB with the dtc
> compiler, and convert it back to the DTS the correct values are shown
>
> (4) If I change the interrupt value:
>
> interrupts = <0xc 0x0>;
>
> and I do:
>
> cat <file-old.dtb> | od -t x1 > file1.txt
> cat <file-mod.dtb> | od -t x1 > file2.txt
> kdiff3 file1.txt file2.txt
>
> I actually see a single hex byte change from 0x1 to 0x0.
>
> If it was not for the faulty fdtdump output (in conjuection with the
> Linux kernel zero at the same place) I would have said its definately
> a kernel issue.
>
> Any ideas?
Well that's certainly weird. Is it possible for you to attach the
whole dts and dtb so I can experiment?
What output does decompiling with dtc -I dtb -O dts give you?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-02 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 17:53 DTB file appears to have corrupted node property according to fdtdump and kernel? Frederik Lotter
[not found] ` <CAPBAm7QSB_-LrAwouztLYLaC0mWF2V4QQ_Yz98p6jVw07SfT6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-02 22:56 ` David Gibson [this message]
2017-02-03 2:28 ` Frank Rowand
[not found] ` <5893EABE.10009-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-03 8:35 ` Frederik Lotter
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=20170202225602.GB7754@umbus.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=frederik.lotter-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).