From: Grant Likely <grant.likely@secretlab.ca>
To: Tony Lindgren <tony@atomide.com>
Cc: Peter Barada <peterb@logicpd.com>,
Mika Westerberg <ext-mika.1.westerberg@nokia.com>,
linux-omap@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: Re: Preventing OMAP3 serial driver to take control of all UARTs
Date: Wed, 2 Dec 2009 08:07:21 -0700 [thread overview]
Message-ID: <fa686aa40912020707p70eb693dp6fcd03facabb5892@mail.gmail.com> (raw)
In-Reply-To: <20091130194031.GV4348@atomide.com>
On Mon, Nov 30, 2009 at 12:40 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Grant Likely <grant.likely@secretlab.ca> [091130 09:01]:
>> http://www.elinux.org/Device_Trees
>>
>> I expect to have my prototype ready for review mid-January, and most
>> of the common code should be either merged or queued up in linux-next
>> by that time.
>
> While device tree is a nice solution to some of the problems, it still
> leaves all the issues we already have with buggy and and outdated
> bootloaders. So we still need to properly initialize the devices in
> the kernel.
Yes, buggy firmware is still a problem. However, if the required
configuration is described in the device tree data, then for some
things the driver can handle setting up the device and the amount of
board-specific code can be reduced.
> Just for reference, most of the omap bootloader bugs seem to be
> related to not muxing the pins right or using wrong timings for GPMC.
>
> And then things that mostly change during the board development are
> the GPIO pins, but those can be easily rewritten in the board-*.c
> files based on the omap_rev.
>
> But at least the device tree is a standard model, while the earlier
> omap tag approach was non-standard.
>
> Peter, maybe you've already thought through all this.. But would it be
> possible to do lightweight device tree that we just use to populate
> the platform data?
This is completely possible. Just having the device tree available
doesn't force the kernel to use it for everything. I've found it
useful to start small and add things as I need them. Most important
thing to remember is to follow the documented & established device
tree conventions so that common code can understand it.
Oh, and speaking of GPIOs, there is a binding for describing GPIO pin
connections in the device tree:
Documentation/powerpc/dts-bindings/gpio/gpio.txt
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-12-02 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 8:46 Preventing OMAP3 serial driver to take control of all UARTs Mika Westerberg
2009-11-30 16:36 ` Peter Barada
2009-11-30 17:01 ` Grant Likely
2009-11-30 19:40 ` Tony Lindgren
2009-11-30 20:31 ` Peter Barada
2009-11-30 21:09 ` Tony Lindgren
2009-12-01 11:02 ` Mika Westerberg
2009-12-09 22:43 ` Kevin Hilman
2009-12-10 10:33 ` [PATCH] OMAP3: serial - allow platforms specify which UARTs to initialize Mika Westerberg
2009-12-11 22:27 ` [APPLIED] [PATCH] OMAP3: serial - allow platforms specify which UARTs to Tony Lindgren
2009-11-30 20:52 ` Preventing OMAP3 serial driver to take control of all UARTs Tony Lindgren
2009-12-02 15:07 ` Grant Likely [this message]
2009-12-02 15:53 ` Olof Johansson
2009-12-02 16:04 ` Grant Likely
2009-12-02 16:16 ` Olof Johansson
2009-12-02 17:24 ` Grant Likely
2009-12-03 0:59 ` Tony Lindgren
2009-12-03 1:00 ` Tony Lindgren
2009-12-03 6:56 ` Mika Westerberg
2009-12-03 8:46 ` Artem Bityutskiy
2009-12-03 19:52 ` Tony Lindgren
2009-12-07 10:44 ` Mika Westerberg
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=fa686aa40912020707p70eb693dp6fcd03facabb5892@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=ext-mika.1.westerberg@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=peterb@logicpd.com \
--cc=tony@atomide.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