All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard clark <richard.xnu.clark@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: will@kernel.org, jean-philippe@linaro.org, mark.rutland@arm.com,
	 yuzenghui@huawei.com
Subject: Re: Question: multiple SMMUv3 devices probe
Date: Thu, 8 Apr 2021 09:31:19 +0800	[thread overview]
Message-ID: <CAJNi4rOdXLbwyhesFuyD0qQQ92Bp-dtwjZnKjQ5=Uhvy7iP9GA@mail.gmail.com> (raw)
In-Reply-To: <CAJNi4rN2myKrRvuPPQg1QikAkbJVpb=fuETK0yV8wt-HNvZq9A@mail.gmail.com>

> Hi guys,
> There're 3 SMMUv3 devices in my arm64 box. I am confused by the below
> probe process:
>
> arm_smmu_device_probe(...) --> arm_smmu_set_bus_ops(&arm_smmu_ops):
> if (platform_bus_type.iommu_ops != ops) {
>         err = bus_set_iommu(&platform_bus_type, ops);
>         if (err)
> }
>
> so for the 1st smmu device on the platform_bus, the
> arm_smmu_device_probe(...) will set the platform_bus_type.iommu_bus =
> arm_smmu_ops, so for the arm_smmu_device_probe(...) when probing the
> 2nd smmu device, the bus_set_iommu() will have no chance be called
> since the platform_bus_type.iommu_bus == arm_smmu_ops is true, my
> question is how the followed bus_set_iommu(...) being called?
>
> Thanks,
> RC

For this question,  any comments about that? Will, the owner of the
device driver, do you have some any? How about others too?
Thanks,
RC

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-04-08  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  9:37 Question: multiple SMMUv3 devices probe richard clark
2021-04-08  1:31 ` richard clark [this message]
2021-04-08  7:25 ` Jean-Philippe Brucker
     [not found]   ` <CAJNi4rPx=oh7iv=4=-5PV-7OAgkZzr5zLysgTjr3YVKzHsC44w@mail.gmail.com>
     [not found]     ` <YHWVWiQpS93lRNly@myrica>
2021-04-14  1:45       ` richard clark
2021-04-14  2:39         ` Zenghui Yu
2021-04-14  3:17           ` richard clark

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='CAJNi4rOdXLbwyhesFuyD0qQQ92Bp-dtwjZnKjQ5=Uhvy7iP9GA@mail.gmail.com' \
    --to=richard.xnu.clark@gmail.com \
    --cc=jean-philippe@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.