public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Jaroslav Kysela <perex@perex.cz>, <broonie@kernel.org>, <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>,
	<amadeuszx.slawinski@linux.intel.com>,
	<pierre-louis.bossart@linux.intel.com>, <hdegoede@redhat.com>
Subject: Re: [PATCH v4 04/16] ALSA: hda: Upgrade stream-format infrastructure
Date: Fri, 17 Nov 2023 12:51:20 +0100	[thread overview]
Message-ID: <e714d741-9333-60f3-a797-c005e2545359@intel.com> (raw)
In-Reply-To: <f4d510a8-de37-494d-b7a8-61770da1db93@perex.cz>



On 2023-11-16 4:10 PM, Jaroslav Kysela wrote:
> On 16. 11. 23 12:22, Cezary Rojewski wrote:
>> Introduce a set of functions that ultimately facilite SDxFMT-related
>> calculations in atomic manner:
>>
>> First, introduce snd_pcm_subformat_width() and snd_pcm_hw_params_bps()
>> helpers that separate the base functionality from the HDAudio-specific
>> one.
> 
> I think, snd_pcm_subformat_width() should be implemented only as static 
> helper for now. There are no users and only snd_pcm_hw_params_bps() 
> makes sense for callers (format & subformat must be passed together).

Ack. Inlining into its only user.

> Also note that _bps is mostly used for bits-per-second in the computer 
> world, so maybe _bpsam may be used here to pay more attention by 
> readers, but it's just my optional proposal. Maybe my head has some 
> "fixed wiring" for this :)

The current shortcut is taken from existing intel/ code which utilizes 
'bps' but I agree that it can be misleading.

What I did to solve the problem: opened both, HDAudio (bare) and 
HDAudio+ADSP specs and in both the relevant fields (the fields that 
relate to bits-per-sample) are called "BITS". Also searched google for 
the 'bits per sample' phrase and one of the first thing that came up was 
audacity doc which used the exact same phrase (bits).

All occurrences of 'bps' will be replaced by 'bits'.


Kind regards,
Czarek

  reply	other threads:[~2023-11-17 11:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 11:22 [PATCH v4 00/16] ALSA/ASoC: hda: Address format selection limitations and ambiguity Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 01/16] ALSA: pcm: Introduce MSBITS subformat interface Cezary Rojewski
2023-11-16 15:10   ` Jaroslav Kysela
2023-11-17 11:45     ` Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 02/16] ALSA: hda: Honor subformat when querying PCMs Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 03/16] ASoC: pcm: Honor subformat when configuring runtime Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 04/16] ALSA: hda: Upgrade stream-format infrastructure Cezary Rojewski
2023-11-16 15:10   ` Jaroslav Kysela
2023-11-17 11:51     ` Cezary Rojewski [this message]
2023-11-16 11:22 ` [PATCH v4 05/16] ALSA: hda: Switch to new stream-format interface Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 06/16] ALSA: hda/hdmi: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 07/16] ALSA: hda/ca0132: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 08/16] ASoC: codecs: hda: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 09/16] ASoC: codecs: hdac_hda: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 10/16] ASoC: codecs: hdac_hdmi: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 11/16] ASoC: Intel Skylake: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 12/16] ASoC: SOF: Intel: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 13/16] ASoC: Intel: avs: " Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 14/16] ALSA: hda: Drop snd_hdac_calc_stream_format() Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 15/16] ASoC: Intel: avs: Kill S24_LE format Cezary Rojewski
2023-11-16 11:22 ` [PATCH v4 16/16] ASoC: Intel: avs: Unhardcode HDAudio BE DAI drivers description Cezary Rojewski

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=e714d741-9333-60f3-a797-c005e2545359@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox