From: Ilya Yanok <yanok@emcraft.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, wd@denx.de, dzu@denx.de, sasha_d@emcraft.com
Subject: Re: [PATCH 4/4] mcx: initial support for HTKW mcx board
Date: Tue, 22 Nov 2011 04:21:07 +0400 [thread overview]
Message-ID: <4ECAEAF3.4080708@emcraft.com> (raw)
In-Reply-To: <20111119003630.GA31337@atomide.com>
Hi Tony,
On 19.11.2011 04:36, Tony Lindgren wrote:
>> Well, it already boots with DT actually. Did you mean booting with DT
>> and board-generic? I have to admit I don't know how to proceed here:
>
> Good to hear you're already playing with it. Yes, let's work on making
> all the boards work with DT and board-generic..
Hm, do you think it's absolutely necessary to make everybody work with
board-generic? It will require a lot of additional bindings to get rid
of all machine-specific code. I've just thought that on PowerPC we don't
have such strict rules: if some boards are really similar they share
common machine file but if we need something specific for the new board
we can create it's own machine file.
>> board-generic initialize twl4030 which we don't have on our board...
>> Could you give me some pointer how I'm supposed to handle this?
>
> .. we should only initialize twl4030/twl6030 if the DT compatible flag
> for it is set. But we're still missing the DT bindings for those :(
>
> For now, maybe try to fix the twl4030 probe so it won't do anything
> unless the I2C device is found?
That turned to be not such a big problem. Device is not present so we
have tons of error messages but somehow it works.
The bigger problem is that we have different regulator chip attached.
How am I supposed to register supplies/consumers data with it? Does
anybody working on DT bindings for the regulator framework?
Regards, Ilya.
next prev parent reply other threads:[~2011-11-22 0:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 0:12 [PATCH 0/4] Support for the HTKW mcx board Ilya Yanok
2011-11-09 0:12 ` [PATCH 1/4] AM35xx: DSS: there is no VDDS_DSI on AM35xx Ilya Yanok
2011-11-09 10:10 ` Archit Taneja
2011-11-09 18:26 ` Ilya Yanok
2011-11-10 6:42 ` Archit Taneja
2011-11-16 21:03 ` Ilya Yanok
2011-11-09 0:12 ` [PATCH 2/4] omap_dss: add FocalTech ETM070003DH6 display support Ilya Yanok
2011-11-17 0:28 ` Ilya Yanok
2011-11-17 6:52 ` Igor Grinberg
2011-11-17 10:26 ` Tomi Valkeinen
2011-11-20 18:12 ` Ilya Yanok
2011-11-20 18:15 ` [PATCH V2] " Ilya Yanok
2011-11-22 10:04 ` Tomi Valkeinen
2011-11-09 0:12 ` [PATCH 3/4] dts/omap3: split omap3.dtsi Ilya Yanok
2011-11-10 12:18 ` Igor Grinberg
2011-11-10 17:09 ` Cousson, Benoit
2011-11-10 17:26 ` Igor Grinberg
2011-11-10 18:07 ` Cousson, Benoit
2011-11-11 7:32 ` Igor Grinberg
2011-11-09 0:12 ` [PATCH 4/4] mcx: initial support for HTKW mcx board Ilya Yanok
2011-11-10 13:08 ` Igor Grinberg
2011-11-11 0:12 ` Tony Lindgren
2011-11-14 20:39 ` Ilya Yanok
2011-11-19 0:36 ` Tony Lindgren
2011-11-22 0:21 ` Ilya Yanok [this message]
2011-12-08 0:04 ` Tony Lindgren
2011-11-13 17:56 ` Pankaj Kumar
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=4ECAEAF3.4080708@emcraft.com \
--to=yanok@emcraft.com \
--cc=dzu@denx.de \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.com \
--cc=tony@atomide.com \
--cc=wd@denx.de \
/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).