On Tue, Apr 11, 2017 at 10:27:55PM +0530, Sunil Kovvuri wrote:
> On Tue, Apr 11, 2017 at 9:29 PM, Robin Murphy <robin.murphy@xxxxxxx> wrote:
> > On 11/04/17 15:42, linucherian@xxxxxxxxx wrote:
> >> From: Linu Cherian <linu.cherian@xxxxxxxxxx>
> >>
> >> Add SMMuV3 model definitions.
> >>
> >> Signed-off-by: Linu Cherian <linu.cherian@xxxxxxxxxx>
> >> ---
> >> include/acpi/actbl2.h | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >> diff --git a/include/acpi/actbl2.h b/include/acpi/actbl2.h
> >> index 2b4af07..9db67d6 100644
> >> --- a/include/acpi/actbl2.h
> >> +++ b/include/acpi/actbl2.h
> >> @@ -778,6 +778,11 @@ struct acpi_iort_smmu {
> >> #define ACPI_IORT_SMMU_CORELINK_MMU400 0x00000002 /* ARM Corelink MMU-400 */
> >> #define ACPI_IORT_SMMU_CORELINK_MMU500 0x00000003 /* ARM Corelink MMU-500 */
> >>
> >> +#define ACPI_IORT_SMMU_V3 0x00000000 /* Generic SMMUv3 */
> >> +#define ACPI_IORT_SMMU_CORELINK_MMU600 0x00000001 /* ARM Corelink MMU-600 */
> >> +#define ACPI_IORT_SMMU_V3_HISILICON 0x00000002 /* HiSilicon SMMUv3 */
> >> +#define ACPI_IORT_SMMU_V3_CAVIUM_CN99XX 0x00000003 /* Cavium CN99xx SMMUv3 */
> >
> > None of those models are listed in the current IORT spec.
>
> As mentioned in the cover letter, we are in the process of getting
> model no added for our silicon in the soon to be published updated
> IORT spec.
Good, so first get the IORT firmware bindings updated and then post
patches to manage them, there is really no point in commenting on
patches based on FW that can't be written.
Thanks,
Lorenzo
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
