On 5/10/17 8:58 PM, Jeremy Kerr wrote:
Hi Chris,
I don't think we'd want this per master. The lock is for the 'top'
master issuing commands. Only the top master can initiate any
transactions on the bus to any devices connected downstream. Downstream
masters such as hub masters, etc... cann
Hi Chris,
> I don't think we'd want this per master. The lock is for the 'top'
> master issuing commands. Only the top master can initiate any
> transactions on the bus to any devices connected downstream. Downstream
> masters such as hub masters, etc... cannot initiate a command.
I think what
On 5/10/17 2:30 AM, Joel Stanley wrote:
Hi Chris,
On Tue, Apr 11, 2017 at 5:17 AM, Christopher Bostic
wrote:
From: Chris Bostic
Implement a FSI master using GPIO. Will generate FSI protocol for
read and write commands to particular addresses. Sends master command
and waits for and decod
Hi Chris,
On Tue, Apr 11, 2017 at 5:17 AM, Christopher Bostic
wrote:
> From: Chris Bostic
>
> Implement a FSI master using GPIO. Will generate FSI protocol for
> read and write commands to particular addresses. Sends master command
> and waits for and decodes a slave response.
>
> Includes ch
From: Chris Bostic
Implement a FSI master using GPIO. Will generate FSI protocol for
read and write commands to particular addresses. Sends master command
and waits for and decodes a slave response.
Includes changes from Edward A. James and Jeremy
Kerr .
Signed-off-by: Edward A. James
Signe
5 matches
Mail list logo