On Fri, Jul 17, 2020 at 01:16:42PM +0200, Arnaud Ferraris wrote:
> Hi Nic,
>
> Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
> > Hi Arnaud,
> >
> > On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
> >> The current ASRC driver hardcodes the input and output clocks used for
> >> sam
Hi Nic,
Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
> Hi Arnaud,
>
> On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
>> The current ASRC driver hardcodes the input and output clocks used for
>> sample rate conversions. In order to allow greater flexibility and to
>> cover more
Le 16/07/2020 à 14:18, Mark Brown a écrit :
> On Wed, Jul 15, 2020 at 02:03:08PM -0700, Nicolin Chen wrote:
>> On Wed, Jul 15, 2020 at 03:05:19PM +0100, Mark Brown wrote:
>>> On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
>
Thanks for the input. Fox i.MX6, I don't feel it wo
On Wed, Jul 15, 2020 at 02:03:08PM -0700, Nicolin Chen wrote:
> On Wed, Jul 15, 2020 at 03:05:19PM +0100, Mark Brown wrote:
> > On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
> > > Thanks for the input. Fox i.MX6, I don't feel it would be that
> > > drastically different though. And
Le 15/07/2020 à 22:46, Nicolin Chen a écrit :
>> Calculations are indeed good, but then the clock selection setting in
>> the ASRCSR register would also use SSI1 as the input clock, which
>> doesn't work in our case.
>
> Could you please elaborate why it doesn't work?
>
Hmm, actually it was a
On Wed, Jul 15, 2020 at 03:05:19PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
> > On Tue, Jul 14, 2020 at 09:27:53PM +0100, Mark Brown wrote:
>
> > > The nominal rate might be the same but if they're in different clock
> > > domains then the actual rat
On Wed, Jul 15, 2020 at 06:18:38PM +0200, Arnaud Ferraris wrote:
> Hi,
>
> Le 15/07/2020 à 16:05, Mark Brown a écrit :
> > On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
> > Anything wrong with ASRC selecting SSI1 clock for both cases? The
> > driver calculates the divisors based on
Le 15/07/2020 à 18:22, Mark Brown a écrit :
>
> Those look reasonable enough off the top of my head, not that I've
> really looked at the hardware.
>
Alright, thanks for your feedback! Unless Nic has other comments I'll
submit a v2 tomorrow then.
Regards,
Arnaud
On Wed, Jul 15, 2020 at 06:18:38PM +0200, Arnaud Ferraris wrote:
> Le 15/07/2020 à 16:05, Mark Brown a écrit :
> > Honestly for anything that fun it tends to be a custom machine driver.
> > A property would seem reasonable though.
> I think so, does my initial implementation of the properties loo
Hi,
Le 15/07/2020 à 16:05, Mark Brown a écrit :
> On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
> Anything wrong with ASRC selecting SSI1 clock for both cases? The
> driver calculates the divisors based on the given clock rate, so
> the final internal rate should be the same. If th
On Tue, Jul 14, 2020 at 01:50:50PM -0700, Nicolin Chen wrote:
> On Tue, Jul 14, 2020 at 09:27:53PM +0100, Mark Brown wrote:
> > The nominal rate might be the same but if they're in different clock
> > domains then the actual rates might be different (hence the desire for
> > an ASRC I guess). I c
Hi Mark,
On Tue, Jul 14, 2020 at 09:27:53PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2020 at 01:15:45PM -0700, Nicolin Chen wrote:
> > On Tue, Jul 14, 2020 at 06:20:32PM +0200, Arnaud Ferraris wrote:
>
> > > Here's some background about my use case: the i.MX6 board acts as a
> > > Bluetooth pro
On Tue, Jul 14, 2020 at 01:15:45PM -0700, Nicolin Chen wrote:
> On Tue, Jul 14, 2020 at 06:20:32PM +0200, Arnaud Ferraris wrote:
> > Here's some background about my use case: the i.MX6 board acts as a
> > Bluetooth proxy between a phone and a headset. It has 2 Bluetooth
> > modules (one for each c
On Tue, Jul 14, 2020 at 06:20:32PM +0200, Arnaud Ferraris wrote:
> >>> The current ASRC driver hardcodes the input and output clocks used for
> >>> sample rate conversions. In order to allow greater flexibility and to
> >>> cover more use cases, it would be preferable to select the clocks using
> >
Hi Nic,
Le 03/07/2020 à 11:38, Arnaud Ferraris a écrit :
> Hi Nic,
>
> Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
>> Hi Arnaud,
>>
>> On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
>>> The current ASRC driver hardcodes the input and output clocks used for
>>> sample rate conv
Hi Nic,
Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
> Hi Arnaud,
>
> On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
>> The current ASRC driver hardcodes the input and output clocks used for
>> sample rate conversions. In order to allow greater flexibility and to
>> cover more
Hi Arnaud,
On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
> The current ASRC driver hardcodes the input and output clocks used for
> sample rate conversions. In order to allow greater flexibility and to
> cover more use cases, it would be preferable to select the clocks using
> d
The current ASRC driver hardcodes the input and output clocks used for
sample rate conversions. In order to allow greater flexibility and to
cover more use cases, it would be preferable to select the clocks using
device-tree properties.
This series also fix register configuration and clock assignm
18 matches
Mail list logo
