Re: [PATCH v2] iommu/io-pgtable: Rationalise quirk handling

2016-02-12 Thread Will Deacon
On Fri, Feb 12, 2016 at 05:09:46PM +, Robin Murphy wrote: > As the number of io-pgtable implementations grows beyond 1, it's time > to rationalise the quirks mechanism before things have a chance to > start getting really ugly and out-of-hand. > > To that end: > - Indicate exactly which quirks

Re: [PATCH v2] iommu/io-pgtable: Rationalise quirk handling

2016-02-12 Thread Robin Murphy
On 12/02/16 17:24, Laurent Pinchart wrote: Hi Robin, Thank you for the patch. On Friday 12 February 2016 17:09:46 Robin Murphy wrote: As the number of io-pgtable implementations grows beyond 1, it's time to rationalise the quirks mechanism before things have a chance to start getting really ug

Re: [PATCH v2] iommu/io-pgtable: Rationalise quirk handling

2016-02-12 Thread Laurent Pinchart
Hi Robin, Thank you for the patch. On Friday 12 February 2016 17:09:46 Robin Murphy wrote: > As the number of io-pgtable implementations grows beyond 1, it's time > to rationalise the quirks mechanism before things have a chance to > start getting really ugly and out-of-hand. > > To that end: >

[PATCH v2] iommu/io-pgtable: Rationalise quirk handling

2016-02-12 Thread Robin Murphy
As the number of io-pgtable implementations grows beyond 1, it's time to rationalise the quirks mechanism before things have a chance to start getting really ugly and out-of-hand. To that end: - Indicate exactly which quirks each format can/does support. - Fail creating a table if a caller wants u