On Mon, 29 Jul 2013 19:41:23 +0200 Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: ... > > I think that this belongs to the system operation policy. Which H/W > > should be configured to which Address Space(AS). This put all AHB > > clients(PPCS) into AS[1](SYSTEM_PROTECTED), and the rest into > > AS[0](SYSTEM_DEFAULT). AHB clients are mainly traditional H/Ws like > > USB and SD/MMC so that they should be kept separated from the smart > > IOMMU clients like host1x. > > > > Is there any place to configure this kind of board specific policy > > rather than here? > > I'm not sure that answers the question I asked. > > I mean that the driver expects that two AS always exist; > SYSTEM_PROTECTED and SYSTEM_DEFAULT. However, the set of extant ASs is > IIRC defined by the DT content. What if the DT doesn't define two ASs? > Shouldn't there at least be an error-check for this case, so the driver > doesn't just blindly continue and access smmu_handle->map[1] when the > map[] array only has 1 entry? OK, now I got it. We can create multiple maps on the same AS in theory. So the limitation is only for how many maps S/W creaed. This can/should be checked only within kernel side. No constraints from DT. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
