From: Jerome Brunet <jbrunet@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
Kevin Hilman <khilman@baylibre.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH 2/4] ASoC: meson: axg-fifo: add fifo depth to the bindings documentation
Date: Wed, 18 Dec 2019 19:13:08 +0100 [thread overview]
Message-ID: <1jimmdbiyz.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20191218175031.GM3219@sirena.org.uk>
On Wed 18 Dec 2019 at 18:50, Mark Brown <broonie@kernel.org> wrote:
> On Wed, Dec 18, 2019 at 06:24:18PM +0100, Jerome Brunet wrote:
>
>> Add a new property with the depth of the fifo in bytes. This is useful
>> since some instance of the fifo, even on the same SoC, may have different
>> depth. The depth is useful is set some parameters of the fifo.
>
> Can't we figure this out from the compatible strings? They look SoC
> specific (which is good). That means we don't need to add new
> properties for each quirk that separates the variants.
I don't think it would be appropriate in this case:
If I take the example of TODDR fifos on the SM1 SoC;
All the TODDR fifo on this SoC are compatible with the same driver and use:
compatible = "amlogic,sm1-toddr", "amlogic,axg-toddr";
However instance A on this SoC has a 8192B fifo while instance B, C and D
have 256B fifo. Same goes for the other SoC and also FRDDR fifos.
To store this difference using compatible I would have to add 1 compatible
string for each "A" instance of each FRDDR and TODDR of each SoC. At the
moment this would be 6 more compatible string for something that is really a
parameter ... This also shows that fifo depth is something the HW
manufacturer can tweak easily for each instances.
It would not scale which is why I went for a property.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-18 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:24 [alsa-devel] [PATCH 0/4] ASoC: meson: axg-fifo: fix depth handling Jerome Brunet
2019-12-18 17:24 ` [alsa-devel] [PATCH 1/4] ASoC: meson: axg-fifo: fix fifo threshold setup Jerome Brunet
2019-12-18 20:05 ` [alsa-devel] Applied "ASoC: meson: axg-fifo: fix fifo threshold setup" to the asoc tree Mark Brown
2019-12-18 17:24 ` [alsa-devel] [PATCH 2/4] ASoC: meson: axg-fifo: add fifo depth to the bindings documentation Jerome Brunet
2019-12-18 17:50 ` Mark Brown
2019-12-18 18:13 ` Jerome Brunet [this message]
2019-12-18 20:05 ` [alsa-devel] Applied "ASoC: meson: axg-fifo: add fifo depth to the bindings documentation" to the asoc tree Mark Brown
2019-12-18 17:24 ` [alsa-devel] [PATCH 3/4] ASoC: meson: axg-fifo: improve depth handling Jerome Brunet
2019-12-18 20:05 ` [alsa-devel] Applied "ASoC: meson: axg-fifo: improve depth handling" to the asoc tree Mark Brown
2019-12-18 17:24 ` [alsa-devel] [PATCH 4/4] ASoC: meson: axg-fifo: relax period size constraints Jerome Brunet
2019-12-18 20:05 ` [alsa-devel] Applied "ASoC: meson: axg-fifo: relax period size constraints" to the asoc tree Mark Brown
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=1jimmdbiyz.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox