From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Constantine Shulyupin <const@MakeLinux.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux@arm.linux.org.uk, tim.bird@am.sony.com,
pandaboard@googlegroups.com,
Santosh Shilimkar OMAP <santosh.shilimkar@ti.com>,
nsekhar@ti.com
Subject: Re: [PATCH] Add FDT support to Pandaboard initialization
Date: Mon, 29 Oct 2012 09:01:23 -0700 [thread overview]
Message-ID: <20121029160122.GB11908@atomide.com> (raw)
In-Reply-To: <20121029061427.GP17570@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [121028 23:22]:
> On Sat, Oct 27, 2012 at 08:50:00PM +0200, Constantine Shulyupin wrote:
> > From: Constantine Shulyupin <const@MakeLinux.com>
> >
> > Problem:
> > - FDT is supported only by generic OMAP board initialization in arch/arm/mach-omap2/board-generic.c and lacks some configurations, which are not yet configured in FDT (USB for example).
> > Solution:
> > - arch/arm/mach-omap2/board-omap4panda.c supports initialization with FDT and without it.
> >
> > Signed-off-by: Constantine Shulyupin <const@MakeLinux.com>
>
> NAK, the whole idea of DT is to drop board-*.c. It would be best to see
> the "missing initialization" being added to board-generic/dts files.
Yes I agree, let's rather get board-generic.c to work with panda.
The other board-*.c files will be dropped as soon as we have
things usable with devicetree. And we're only two board-*.c files
away from making omap4 device tree only ;)
I think we are only missing DSS, USB and WLAN bindings to
have blaze and panda usable with device tree to the point
where everything else can be added later on.
Regards,
Tony
prev parent reply other threads:[~2012-10-29 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 18:50 [PATCH] Add FDT support to Pandaboard initialization Constantine Shulyupin
2012-10-29 6:14 ` Felipe Balbi
2012-10-29 16:01 ` Tony Lindgren [this message]
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=20121029160122.GB11908@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=const@MakeLinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=pandaboard@googlegroups.com \
--cc=santosh.shilimkar@ti.com \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).