From: Ilya Yanok <yanok@emcraft.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-omap@vger.kernel.org, sasha_d@emcraft.com,
Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH V2 1/2] mcx: very basic support for HTKW mcx board
Date: Fri, 16 Dec 2011 01:59:13 +0400 [thread overview]
Message-ID: <4EEA6DB1.8040206@emcraft.com> (raw)
In-Reply-To: <4EE9C31B.7080206@compulab.co.il>
Hi Igor,
On 15.12.2011 13:51, Igor Grinberg wrote:
>> + /* AM35xx doesn't have IVA */
>> + soc {
>> + iva {
>> + status = "disabled";
>> + };
>> + };
>
> I don't get it...
> Why SoCs that do not have those IP blocks should poke
> their configuration inside the h/w description
> (e.g. disable/enable/workaround/hack)?
> This way, why don't we also disable the PCIe which this SoC does not have?
Well, I'm not really happy about this solution... But when we discussed
it last time (http://thread.gmane.org/gmane.linux.ports.arm.omap/66601 )
you and Benoit didn't come to agreement...
I really like your solution with dts built from brick corresponding to
IPs but I don't have much time to invest into patches that will likely
be rejected...
Regards, Ilya.
next prev parent reply other threads:[~2011-12-15 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 0:53 [PATCH V2 0/2] Support for HTKW mcx Ilya Yanok
2011-12-15 0:53 ` [PATCH V2 1/2] mcx: very basic support for HTKW mcx board Ilya Yanok
2011-12-15 9:51 ` Igor Grinberg
2011-12-15 10:17 ` Cousson, Benoit
2011-12-15 10:53 ` Igor Grinberg
2011-12-18 13:21 ` Igor Grinberg
2011-12-15 21:59 ` Ilya Yanok [this message]
2011-12-17 1:37 ` Tony Lindgren
2012-01-11 22:03 ` Ilya Yanok
2011-12-15 0:53 ` [PATCH V2 2/2] mcx: " Ilya Yanok
2011-12-15 10:40 ` Igor Grinberg
2011-12-20 20:07 ` Ilya Yanok
2011-12-21 9:19 ` Igor Grinberg
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=4EEA6DB1.8040206@emcraft.com \
--to=yanok@emcraft.com \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=grinberg@compulab.co.il \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.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;
as well as URLs for NNTP newsgroup(s).