All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
	alsa-devel@alsa-project.org, Timur Tabi <timur@kernel.org>,
	Xiubo Li <Xiubo.Lee@gmail.com>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	kernel@collabora.com, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks
Date: Wed, 15 Jul 2020 17:22:02 +0100	[thread overview]
Message-ID: <20200715162202.GJ5431@sirena.org.uk> (raw)
In-Reply-To: <0a56326b-27a9-d9f4-3923-8773963d7548@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

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 look
> sensible to you? ("fsl,asrc-input-clock" & "fsl,asrc-output-clock")

Those look reasonable enough off the top of my head, not that I've
really looked at the hardware.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Cc: alsa-devel@alsa-project.org, Timur Tabi <timur@kernel.org>,
	Xiubo Li <Xiubo.Lee@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Takashi Iwai <tiwai@suse.com>,
	linux-kernel@vger.kernel.org,
	Nicolin Chen <nicoleotsuka@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	kernel@collabora.com, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks
Date: Wed, 15 Jul 2020 17:22:02 +0100	[thread overview]
Message-ID: <20200715162202.GJ5431@sirena.org.uk> (raw)
In-Reply-To: <0a56326b-27a9-d9f4-3923-8773963d7548@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

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 look
> sensible to you? ("fsl,asrc-input-clock" & "fsl,asrc-output-clock")

Those look reasonable enough off the top of my head, not that I've
really looked at the hardware.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-15 16:22 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 14:22 [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks Arnaud Ferraris
2020-07-02 14:22 ` Arnaud Ferraris
2020-07-02 14:22 ` Arnaud Ferraris
2020-07-02 14:22 ` [PATCH 1/4] dt-bindings: sound: fsl,asrc: add properties to select in/out clocks Arnaud Ferraris
2020-07-02 14:22   ` [PATCH 1/4] dt-bindings: sound: fsl, asrc: " Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 14:22 ` [PATCH 2/4] ASoC: fsl_asrc: allow using arbitrary input and output clocks Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 17:42   ` kernel test robot
2020-07-02 21:33   ` kernel test robot
2020-07-02 14:22 ` [PATCH 3/4] ASoC: fsl_asrc: always use ratio for conversion Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 14:22 ` [PATCH 4/4] ASoC: fsl_asrc: swap input and output clocks in capture mode Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 14:22   ` Arnaud Ferraris
2020-07-02 19:34   ` kernel test robot
2020-07-02 18:42 ` [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks Nicolin Chen
2020-07-02 18:42   ` Nicolin Chen
2020-07-02 18:42   ` Nicolin Chen
2020-07-03  9:38   ` Arnaud Ferraris
2020-07-03  9:38     ` Arnaud Ferraris
2020-07-14 16:20     ` Arnaud Ferraris
2020-07-14 16:20       ` Arnaud Ferraris
2020-07-14 20:15       ` Nicolin Chen
2020-07-14 20:15         ` Nicolin Chen
2020-07-14 20:27         ` Mark Brown
2020-07-14 20:27           ` Mark Brown
2020-07-14 20:50           ` Nicolin Chen
2020-07-14 20:50             ` Nicolin Chen
2020-07-15 14:05             ` Mark Brown
2020-07-15 14:05               ` Mark Brown
2020-07-15 16:18               ` Arnaud Ferraris
2020-07-15 16:18                 ` Arnaud Ferraris
2020-07-15 16:22                 ` Mark Brown [this message]
2020-07-15 16:22                   ` Mark Brown
2020-07-15 16:32                   ` Arnaud Ferraris
2020-07-15 16:32                     ` Arnaud Ferraris
2020-07-15 20:46                 ` Nicolin Chen
2020-07-15 20:46                   ` Nicolin Chen
2020-07-16  9:54                   ` Arnaud Ferraris
2020-07-16  9:54                     ` Arnaud Ferraris
2020-07-15 21:03               ` Nicolin Chen
2020-07-15 21:03                 ` Nicolin Chen
2020-07-16 12:18                 ` Mark Brown
2020-07-16 12:18                   ` Mark Brown
2020-07-16 14:26                   ` Arnaud Ferraris
2020-07-16 14:26                     ` Arnaud Ferraris
2020-07-17 11:16   ` Arnaud Ferraris
2020-07-17 11:16     ` Arnaud Ferraris
2020-07-17 11:16     ` Arnaud Ferraris
2020-07-23  5:46     ` Nicolin Chen
2020-07-23  5:46       ` Nicolin Chen
2020-07-23  5:46       ` Nicolin Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200715162202.GJ5431@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.ferraris@collabora.com \
    --cc=festevam@gmail.com \
    --cc=kernel@collabora.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=timur@kernel.org \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.