From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v02 3/3] xen/arm: add DRA7 platform definition Date: Wed, 02 Jul 2014 16:18:16 +0100 Message-ID: <53B422B8.8080209@linaro.org> References: <1404309000-27846-1-git-send-email-andrii.tseglytskyi@globallogic.com> <1404309000-27846-4-git-send-email-andrii.tseglytskyi@globallogic.com> <53B411B1.2070807@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrii Tseglytskyi Cc: Stefano Stabellini , Chen Baozi , Tim Deegan , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 07/02/2014 04:02 PM, Andrii Tseglytskyi wrote: > Hi Julien, Hi Andrii, > Do you mean this code? Yes. Sorry I wasn't very clear on my previous email. > +static const struct dt_device_match omap5_blacklist_dev[] __initconst = > +{ > + /* OMAP Linux kernel handles devices with status "disabled" in a > + * weird manner - tries to reset them. While their memory ranges > + * are not mapped, this leads to data aborts, so skip these devices > + * from DT for dom0. > + */ > + DT_MATCH_NOT_AVAILABLE(), > + { /* sentinel */ }, > +}; > + > +PLATFORM_START(omap5, "TI OMAP5") > + .compatible = omap5_dt_compat, > + .init_time = omap5_init_time, > + .cpu_up = cpu_up_send_sgi, > + .smp_init = omap5_smp_init, > + > + .dom0_gnttab_start = 0x4b000000, > + .dom0_gnttab_size = 0x20000, > + *.blacklist_dev = omap5_blacklist_dev,* > +PLATFORM_END > > And do not use standalone DRA7 ? Right. If case of someone want to keep DRA7 standalone, you will have to create 2 distinct compatible list. Regards, -- Julien Grall