All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: snd_soc_component_driver substream ops
Date: 27 Jul 2020 07:13:23 +0900	[thread overview]
Message-ID: <877duqylh5.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <CAEnQRZC4FNrLSbasRH4Au=W_tHyQUV_y0WOn-RDZboEhnf0e+g@mail.gmail.com>


Hi Daniel

Thank you for asking
And sorry for late response, Japan was holiday.

> Looking at snd_soc_component_driver I see there
> are some operations like: open, close, hw_params, hw_free. (1)
> 
> Now, snd_soc_component_driver has snd_compress_ops.
> 
> Do you think it is worth it to group operations from (1) in a similar structure
> maybe snd_<xyz>_ops.

It seems snd_soc_component_driver is using many functions and flags.
Keeping these in the some structure is better, IMO.

I think separating "component" and "compress" is better cleaning ?

	struct snd_compress_ops {
		...
	};

	struct snd_soc_component_driver {
		...
-		const struct snd_compress_ops *compress_ops;
		...
	};

	struct snd_soc_component {
		...
		struct snd_soc_component_driver *driver;
+		const struct snd_compress_ops *compress_ops;
		...
	};	


Thank you for your help !!

Best regards
---
Kuninori Morimoto

  reply	other threads:[~2020-07-26 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 16:05 snd_soc_component_driver substream ops Daniel Baluta
2020-07-26 22:13 ` Kuninori Morimoto [this message]
2020-07-27  9:40   ` Daniel Baluta

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=877duqylh5.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel.baluta@gmail.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.