[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180417160908.GH8973@sirena.org.uk>
Date: Tue, 17 Apr 2018 17:09:08 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
Alex Deucher <alexander.deucher@....com>,
Akshu Agrawal <akshu.agrawal@....com>,
Lubomir Rintel <lkundrak@...sk>,
Markus Elfring <elfring@...rs.sourceforge.net>,
Jose Abreu <Jose.Abreu@...opsys.com>,
"Gustavo A. R. Silva" <garsilva@...eddedor.com>,
"moderated list:SOUND" <alsa-devel@...a-project.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] ASoC: dwc: I2S Controller instance param added
On Tue, Apr 17, 2018 at 10:29:51AM +0530, Vijendar Mukunda wrote:
> +#define I2S_SP_INSTANCE 1
> +#define I2S_BT_INSTANCE 2
This is obviously very specific to the system you're working with and
therefore doesn't belong in the generic driver. The device should be
dealing with its own configuration, it shouldn't need to know about what
specifically is connected to it. It's not even clear what they're doing
in this driver given that there doesn't appear to be any use of the
information, it feels like this is something that the machine driver
should be encapsulating.
Like I said with previous reviews this use of magic numbers for the
interfaces is a bit of a red flag, internally within a driver they're
fine but they shouldn't leak out too much except with things like
numbering an array.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists