From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: gpio-pxa initcall level change and machine init breakage
Date: Fri, 26 Apr 2013 19:48:12 +0200 [thread overview]
Message-ID: <87li85yyhv.fsf@free.fr> (raw)
In-Reply-To: <CACRpkdYEi7i_kSuUy4dBW-tE4BxifJY5wFdYVyLe6La5=HwEmg@mail.gmail.com> (Linus Walleij's message of "Thu, 25 Apr 2013 23:22:13 +0200")
Linus Walleij <linus.walleij@linaro•org> writes:
> On Thu, Apr 25, 2013 at 9:36 PM, Robert Jarzmik <robert.jarzmik@free•fr> wrote:
> This was done by pull request to Torvalds yesterday ...
Thanks, that's a relief.
>
>> (b) inform board maintainers that they must fix their board code (for example
>> give them 1 window)
>> (c) put back the patch. Board maintainers who did not amend their board
>> code cannot say anymore they didn't know it. Board maintainers will also have
>> time to rise objections if they think they cannot change their board code
>> (which I do not believe is possible, but who knows ...)
>
> So when it comes to the PXA there is maybe this list of things that
> would be nice to change, and this is likely on top of it ... moving the
> PXA machines over to device tree would be more important if people
> who like them want them so stay around, because non-device tree
> platforms will at some point become deprecated, and fixing the platforms
> to support device tree will inevitably lead to this problem being fixed
> as well.
Yeah, probably. That's a good long term goal too.
Now you reverted, I'm under pressure to fix mioa701 to get rid of gpio calls in
its board setup code :)
As for device tree conversion, well that's another story.
For my case for example I'll have to redevelop the bootloader (IPL+SPL) in order
for suspend to RAM to work ... no world is perfecgt.
Cheers.
--
Robert
next prev parent reply other threads:[~2013-04-26 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 15:26 gpio-pxa initcall level change and machine init breakage Mike Dunn
2013-04-21 6:02 ` Haojian Zhuang
2013-04-21 22:23 ` Mike Dunn
2013-04-22 0:58 ` Haojian Zhuang
2013-04-23 7:26 ` Linus Walleij
2013-04-23 7:49 ` Haojian Zhuang
2013-04-23 19:42 ` Mike Dunn
2013-04-24 19:37 ` Linus Walleij
2013-04-25 19:36 ` Robert Jarzmik
2013-04-25 21:22 ` Linus Walleij
2013-04-26 17:48 ` Robert Jarzmik [this message]
2013-04-26 12:38 ` Mike Dunn
2013-04-24 16:07 ` Mike Dunn
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=87li85yyhv.fsf@free.fr \
--to=robert.jarzmik@free$(echo .)fr \
--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