From: "Çağlar Kilimci" <ckilimci@gmail.com>
To: Jan Remmet <J.Remmet@phytec.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: State Framework and dtb
Date: Tue, 4 Apr 2017 13:27:37 +0300 [thread overview]
Message-ID: <CAGUZs0==LajQvqc2STju-Ohx=T--yFFed1EzrJTUi5TCF2qBbw@mail.gmail.com> (raw)
In-Reply-To: <58e3539f.0582540a.1e64d.751fSMTPIN_ADDED_BROKEN@mx.google.com>
Hey,
2017-04-04 11:04 GMT+03:00 Jan Remmet <J.Remmet@phytec.de>:
> On Mon, Apr 03, 2017 at 11:59:50PM +0300, Çağlar Kilimci wrote:
>> Hello,
>>
>> 2017-03-31 16:00 GMT+03:00 Sascha Hauer <s.hauer@pengutronix.de>:
>> > On Fri, Mar 31, 2017 at 02:41:19PM +0300, Çağlar Kilimci wrote:
>> >> Hey,
>> >>
>> >>
>> >> I tried but got the same result and then I would like to apply your
>> >> serious patch series of the state framework but release that our
>> >> working branch is 2016.07 so could not apply patches. Let me update
>> >> barebox and apply those patches. Are those based on master branch
>> >> right? Or, which branch do you recommend to work on?
>> >
>> > The patches are based on master, yes. Anyway, you seem to have a problem
>> > in getting your changes in the dts file to the running barebox. Please
>> > try to add some nodes/properties to your dts file and verify that a
>> > of_dump shows these nodes. Before that is the case it's not worth to
>> > look any further.
>>
>> Finally, I updated and patched the code and now I can see state@0
>> device in the of_dump:
>> state@0 {
>> magic = <0x27031977>;
>> compatible = "barebox,state";
>> backend-type = "raw";
>> backend = <0x42>;
>> foo {
>> reg = <0x0 0x4>;
>> type = "uint32";
>> default = <0x0>;
>> };
>> bar {
>> reg = <0x10 0x4>;
>> type = "enum32";
>> names = "baz", "qux";
>> default = <0x1>;
>> };
>> };
>
> Here a working example for barebox 2016.11.0 so there may be changes with the
> actual state cleanup patches
>
> + state2: state_socket {
> + magic = <0x456ef363>;
> + compatible = "barebox,state";
> + backend-type = "raw";
> + backend = &eeprom;
I changed to:
backend = <&eeprom>;
then it works :)
barebox@Phytec phyCORE AM335x:/ state
registered state instances:
state_socket (backend: raw, path: /dev/eeprom0)
>
> Maybe the missing backend-storage-type is a problem?
As a documentation, it should not be.
Thank you all.
--
Çağlar Kilimci
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-04-04 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:24 Çağlar Kilimci
2017-03-30 6:31 ` Sascha Hauer
2017-03-30 10:33 ` Çağlar Kilimci
2017-03-31 6:21 ` Sascha Hauer
2017-03-31 6:54 ` Çağlar Kilimci
2017-03-31 7:02 ` Sascha Hauer
2017-03-31 7:18 ` Çağlar Kilimci
2017-03-31 7:23 ` Sascha Hauer
2017-03-31 11:41 ` Çağlar Kilimci
2017-03-31 13:00 ` Sascha Hauer
2017-04-03 20:59 ` Çağlar Kilimci
2017-04-04 6:22 ` Sascha Hauer
2017-04-04 6:49 ` Çağlar Kilimci
2017-04-04 8:04 ` Jan Remmet
[not found] ` <58e3539f.0582540a.1e64d.751fSMTPIN_ADDED_BROKEN@mx.google.com>
2017-04-04 10:27 ` Çağlar Kilimci [this message]
2017-04-04 10:48 ` Ian Abbott
2017-04-05 6:01 ` Sascha Hauer
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='CAGUZs0==LajQvqc2STju-Ohx=T--yFFed1EzrJTUi5TCF2qBbw@mail.gmail.com' \
--to=ckilimci@gmail.com \
--cc=J.Remmet@phytec.de \
--cc=barebox@lists.infradead.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