Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 15 Jul 2020 15:05:19 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Nicolin Chen <nicoleotsuka@gmail.com>
Cc:     Arnaud Ferraris <arnaud.ferraris@collabora.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
Message-ID: <20200715140519.GH5431@sirena.org.uk>
References: <20200702142235.235869-1-arnaud.ferraris@collabora.com>
 <20200702184226.GA23935@Asurada-Nvidia>
 <3f39a0bb-a766-f646-28b3-a51cf9983c6b@collabora.com>
 <3fea8912-63df-ff27-0c29-6284a85107ab@collabora.com>
 <20200714201544.GA10501@Asurada-Nvidia>
 <20200714202753.GM4900@sirena.org.uk>
 <20200714205050.GB10501@Asurada-Nvidia>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="5vjQsMS/9MbKYGLq"
Content-Disposition: inline
In-Reply-To: <20200714205050.GB10501@Asurada-Nvidia>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--5vjQsMS/9MbKYGLq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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 can see the system wanting to choose one clock or
> > the other on the basis of some system specific property (quality of the
> > clock sources, tolerances of the devices involved or something) though
> > it's a rather fun edge case configuration :/ .

> Thanks for the input. Fox i.MX6, I don't feel it would be that
> drastically different though. And both SSI1 and SSI2 can simply
> select the same root clock source to avoid that happen.

If you've got two radios that both need to sync to some radio derived
frequency it gets a bit more entertaining.

> Yet, in case that we need to support such an edge case, what's
> a relatively common practice to allow system select the clock
> source now?

Honestly for anything that fun it tends to be a custom machine driver.
A property would seem reasonable though.

--5vjQsMS/9MbKYGLq
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl8PDR8ACgkQJNaLcl1U
h9B3vQf/f9mEX7hrtyk9FWvaZgsqLq+mUUNALFg5rWK6DoRHzdL5zBIlHuZUkcxD
dwIy0B20CLI43Xtu8/yIkVbPb9X5f2FfoJ0Jo9+R5I6yP6QIMR7ZVVbFwpsCoMGe
nuf4HosTeun7cv9MbTQe/wMbF2kWdX/xPZyEN/DGDvXLs1e/vQHjg0g92LZYLK/A
5tLPFNHJQULz/QKxzHxCdgwNKeA5jKvSZK8I6jNBa+7HKFXbZl07pUGHpSEQ6aFI
iuvyUH8NtvVj+P9f41yHAj3er2TEmpEg98M0JEmE61dahy+oGSivEyqcmJlfKxxd
4nn2FfBH1xDjNZn2ShW+vYcooN+k0A==
=X4/g
-----END PGP SIGNATURE-----

--5vjQsMS/9MbKYGLq--