On 13 March 2018 at 09:23, Maxime Ripard wrote:
> On Tue, Mar 13, 2018 at 09:15:49AM +0100, Code Kipper wrote:
>> On 13 March 2018 at 09:00, Maxime Ripard wrote:
>> > On Mon, Mar 12, 2018 at 04:57:51PM +0100, codekip...@gmail.com wrote:
>> >> From: Marcus Cooper
>> >>
>> >> The i2s block support
On Tue, Mar 13, 2018 at 09:15:49AM +0100, Code Kipper wrote:
> On 13 March 2018 at 09:00, Maxime Ripard wrote:
> > On Mon, Mar 12, 2018 at 04:57:51PM +0100, codekip...@gmail.com wrote:
> >> From: Marcus Cooper
> >>
> >> The i2s block supports multi-lane i2s output however this functionality
> >>
On 13 March 2018 at 09:00, Maxime Ripard wrote:
> On Mon, Mar 12, 2018 at 04:57:51PM +0100, codekip...@gmail.com wrote:
>> From: Marcus Cooper
>>
>> The i2s block supports multi-lane i2s output however this functionality
>> is only possible in earlier SoCs where the pins are exposed and for
>> th
On Mon, Mar 12, 2018 at 04:57:51PM +0100, codekip...@gmail.com wrote:
> From: Marcus Cooper
>
> The i2s block supports multi-lane i2s output however this functionality
> is only possible in earlier SoCs where the pins are exposed and for
> the i2s block used for HDMI audio on the later SoCs.
>
>
4 matches
Mail list logo
