From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v6 5/6] xen: arm: Import of_bus PCI entry from Linux (as a dt_bus entry)
Date: Mon, 6 Jul 2015 11:59:32 +0100	[thread overview]
Message-ID: <559A5F94.7080206@citrix.com> (raw)
In-Reply-To: <1435938972-18288-5-git-send-email-ian.campbell@citrix.com>
Hi Ian,
On 03/07/15 16:56, Ian Campbell wrote:
> This provides specific handlers for the PCI bus relating to matching
> and translating. It's mostly similar to the defaults but includes some
> additional error checks and other PCI specific bits.
> 
> There are some subtle differences in how the generic code vs. the pci
> specific code here will handle buggy DTs (i.e. #*-cells which are not
> as required by the pci bindings). This will mean we tolerate such
> device trees better.
> 
> I say "buggy", but actually it's not clear to me from reading "PCI Bus
> Binding to Open Firmware" that when the device_type is "pci" that
> e.g. the text says "The value of "#address-cells" for PCI Bus Nodes is
> 3." and not "A PCI Bus Node must contain a #address-cells property
> containing 3", iow the #address-cells might validly be implicit rather
> than an actual property. Maybe that interpretation is bogus, but with
> this patch we are are able to cope with DTs written by people who do
> read it like that.
> 
> It also gets us the ability to parse the flags (cacheability),
> although at the moment we only check them for validity rather than use
> them.
> 
> Functions/types renamed and reindented (because apparently we do
> that for these).
> 
> Needs a selection of IORESOURCE_* defines, which I've taken from Linux
> and have included locally for now until we figure out where else they
> might be needed.
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Reviewed-by: Julien Grall <julien.grall@citrix.com>
Regards,
-- 
Julien Grall
next prev parent reply	other threads:[~2015-07-06 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 15:55 [PATCH v6 0/6] xen: arm: Parse PCI DT nodes' ranges and interrupt-map Ian Campbell
2015-07-03 15:56 ` [PATCH v6 1/6] xen: dt: add dt_for_each_irq_map helper Ian Campbell
2015-07-03 15:56 ` [PATCH v6 2/6] xen: dt: add dt_for_each_range helper Ian Campbell
2015-07-03 15:56 ` [PATCH v6 3/6] xen: arm: drop redundant extra call to vgic_reserve_virq Ian Campbell
2015-07-03 15:56 ` [PATCH v6 4/6] xen: arm: map child MMIO and IRQs to dom0 for PCI bus DT nodes Ian Campbell
2015-07-06 10:58   ` Julien Grall
2015-07-03 15:56 ` [PATCH v6 5/6] xen: arm: Import of_bus PCI entry from Linux (as a dt_bus entry) Ian Campbell
2015-07-06 10:59   ` Julien Grall [this message]
2015-07-03 15:56 ` [PATCH v6 6/6] xen: arm: consolidate mmio and irq mapping to dom0 Ian Campbell
2015-07-06 11:02   ` Julien Grall
2015-07-06 11:04 ` [PATCH v6 0/6] xen: arm: Parse PCI DT nodes' ranges and interrupt-map Julien Grall
2015-07-06 13:56   ` Ian Campbell
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=559A5F94.7080206@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).