On Mon, Feb 5, 2018 at 4:37 PM, Rob Herring wrote:
> On Tue, Jan 30, 2018 at 04:21:15PM +1030, Joel Stanley wrote:
>> From: Christopher Bostic
>>
>> Add an optional FSI master property 'no-scan-on-init. This
>> can be specified to indicate that a
On Mon, Feb 5, 2018 at 4:37 PM, Rob Herring wrote:
> On Tue, Jan 30, 2018 at 04:21:15PM +1030, Joel Stanley wrote:
>> From: Christopher Bostic
>>
>> Add an optional FSI master property 'no-scan-on-init. This
>> can be specified to indicate that a master should not be
>> automatically scanned at
On Tue, Jan 30, 2018 at 04:21:15PM +1030, Joel Stanley wrote:
> From: Christopher Bostic
>
> Add an optional FSI master property 'no-scan-on-init. This
> can be specified to indicate that a master should not be
> automatically scanned at init time. This is required
On Tue, Jan 30, 2018 at 04:21:15PM +1030, Joel Stanley wrote:
> From: Christopher Bostic
>
> Add an optional FSI master property 'no-scan-on-init. This
> can be specified to indicate that a master should not be
> automatically scanned at init time. This is required in cases
> where a scan
From: Christopher Bostic
Add an optional FSI master property 'no-scan-on-init. This
can be specified to indicate that a master should not be
automatically scanned at init time. This is required in cases
where a scan could interfere with another FSI master on the
From: Christopher Bostic
Add an optional FSI master property 'no-scan-on-init. This
can be specified to indicate that a master should not be
automatically scanned at init time. This is required in cases
where a scan could interfere with another FSI master on the same
bus.
Signed-off-by:
6 matches
Mail list logo