On Thu, 17 Sep 2015 11:00:59 -0700
David Daney <ddaney.cavm@xxxxxxxxx> wrote:
Hi David,
> From: David Daney <david.daney@xxxxxxxxxx>
>
> Search up the device hierarchy to find devices with a "msi-map"
> property, if found apply the mapping to the GIC device id.
>
> Signed-off-by: David Daney <david.daney@xxxxxxxxxx>
> ---
> drivers/irqchip/irq-gic-v3-its-pci-msi.c | 73 ++++++++++++++++++++++++++++++++
> 1 file changed, 73 insertions(+)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its-pci-msi.c b/drivers/irqchip/irq-gic-v3-its-pci-msi.c
> index cf351c6..aa61cef 100644
> --- a/drivers/irqchip/irq-gic-v3-its-pci-msi.c
> +++ b/drivers/irqchip/irq-gic-v3-its-pci-msi.c
> @@ -73,6 +73,8 @@ static int its_pci_msi_prepare(struct irq_domain *domain, struct device *dev,
> struct pci_dev *pdev;
> struct its_pci_alias dev_alias;
> struct msi_domain_info *msi_info;
> + struct device *parent_dev;
> + struct device_node *msi_controller_node = NULL;
>
> if (!dev_is_pci(dev))
> return -EINVAL;
> @@ -84,6 +86,77 @@ static int its_pci_msi_prepare(struct irq_domain *domain, struct device *dev,
> dev_alias.count = nvec;
>
> pci_for_each_dma_alias(pdev, its_get_pci_alias, &dev_alias);
> + /*
> + * Walk up the device parent links looking for one with a
> + * "msi-map" property.
> + */
My first objection is the location of this parsing. It shouldn't be
driver specific, but instead be part of the generic OF handling
(nothing in these properties is GICv3 specific, even if the ITS is the
only user so far).
> + for (parent_dev = dev; parent_dev; parent_dev = parent_dev->parent) {
Is there a limit how far we should go up the parent chain to find a
msi-map? My hunch is that you should stop at the first device that does
have an of_node, as it is the one that should contain the msi-map
property.
> + u32 msi_mask, masked_devid;
> + u32 rid_base, msi_base, rid_len, phandle;
> + int msi_map_len;
> + const __be32 *msi_map;
> + bool matched;
> +
> + if (!parent_dev->of_node)
> + continue;
> +
> + msi_map = of_get_property(parent_dev->of_node,
> + "msi-map", &msi_map_len);
> + if (!msi_map)
> + continue;
At this point, you know you do have a msi-map, and anything below this
point won't result in another iteration - they can be taken out of the
loop, avoiding most of your break statements.
> +
> + /* The default is to select all bits. */
> + msi_mask = 0xffffffff;
> +
> + /*
> + * Can be overridden by "msi-mask" property. If
> + * of_property_read_u32() fails, the default is
> + * used.
> + */
> + of_property_read_u32(parent_dev->of_node,
> + "msi-mask", &msi_mask);
This should be "msi-map-mask", if I read Mark's binding correctly.
> +
> + masked_devid = msi_mask & dev_alias.dev_id;
> + matched = false;
> + while (msi_map_len >= 4 * sizeof(__be32)) {
> + rid_base = be32_to_cpup(msi_map + 0);
> + phandle = be32_to_cpup(msi_map + 1);
> + msi_base = be32_to_cpup(msi_map + 2);
> + rid_len = be32_to_cpup(msi_map + 3);
Ouch. I wonder if that kind of thing should deserve a generic helper.
of_property_read_u32_array_from_index()? Rob, what do you think?
Also, worth checking that msi_map_len is multiple of 4 (and shout if
it isn't).
> +
> + if (masked_devid < rid_base ||
> + masked_devid >= rid_base + rid_len) {
> + msi_map_len -= 4 * sizeof(__be32);
> + msi_map += 4;
> + continue;
> + }
> + matched = true;
> + break;
> + }
> + if (!matched) {
> + dev_err(dev,
> + "No match in \"msi-map\" of %s for dev_id: %x\n",
> + dev_name(parent_dev), dev_alias.dev_id);
It would probably be useful to also print the node containing the
msi-map property, as this is likely to be the source of the problem.
> + break;
> + }
> +
> + msi_controller_node = of_find_node_by_phandle(phandle);
> + if (domain->of_node != msi_controller_node) {
> + dev_err(dev,
> + "ERROR: msi-map mismatch \"%s\" vs. \"%s\"\n",
> + domain->of_node->full_name,
> + msi_controller_node ? NULL : msi_controller_node->full_name);
Why is that an error? a RC can be configured to master multiple
MSI-controllers, and the kernel picks one of them for a given device.
This is illustrated by "Example (5)" in the binding, where a device can
master two MSI controllers.
> + break;
> + }
> + dev_dbg(dev,
> + "msi-map at: %s, len: %d, using mask %08x, rid: %08x, msi: %08x, rid_len: %08x, dev_id: %08x\n",
> + dev_name(parent_dev), msi_map_len, msi_mask, rid_base,
> + msi_base, rid_len, dev_alias.dev_id);
> + dev_alias.dev_id = masked_devid + msi_base;
> + dev_dbg(dev, "New dev_id: %08x\n", dev_alias.dev_id);
> + break;
> + }
> + of_node_put(msi_controller_node);
>
> /* ITS specific DeviceID, as the core ITS ignores dev. */
> info->scratchpad[0].ul = dev_alias.dev_id;
Thanks,
M.
--
Jazz is not dead. It just smells funny.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
