All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Keyon Jie <yang.jie@linux.intel.com>
Subject: Re: Why open-coding in sof_hda_bus_init()?
Date: Fri, 31 May 2019 21:06:25 +0200	[thread overview]
Message-ID: <s5hzhn2jvf2.wl-tiwai@suse.de> (raw)
In-Reply-To: <a2737284-ee55-59e5-cab7-2503d27c92bb@linux.intel.com>

On Fri, 31 May 2019 20:31:33 +0200,
Pierre-Louis Bossart wrote:
> 
> On 5/31/19 1:22 PM, Takashi Iwai wrote:
> > On Fri, 31 May 2019 19:43:59 +0200,
> > Pierre-Louis Bossart wrote:
> >>
> >> On 5/31/19 12:11 PM, Takashi Iwai wrote:
> >>> Hi,
> >>>
> >>> while looking at SOF code due to the recent debugging session, I
> >>> noticed that sof_hda_bus_init() is basically an open-code of the
> >>> existing snd_hdac_ext_bus_init().  Why don't we simply call
> >>> snd_hdac_ext_bus_init() like below?
> >>
> >> It's intentional.
> >> We've been asked since Day1 of SOF on ApolloLake to provide a
> >> 'self-contained' controller-only support that has no dependency on the
> >> snd_hdac library for solutions where HDaudio links+codecs are not used
> >> (typically IOT devices). This was driven by the lack of separation
> >> between layers in that library as well as a desire to have a
> >> dual-license. That's why you see the init and some of the basic
> >> utilities re-implemented for SOF.
> >>
> >> However for cases where HDaudio+HDMI are required, we didn't want to
> >> reinvent the wheel - HDaudio is complicated enough - and do make use
> >> of this snd_hdac library.
> >>
> >> We have a config SND_SOC_SOF_HDA that controls in which mode we
> >> operate, and it enables HDMI by default (for I2S+HDMI solutions). To
> >> get external HDaudio codecs you need the additional SOF_HDAUDIO_CODEC
> >> kconfig.
> >>
> >> Does this help?
> >
> > Well, what's wrong with the conditional build with Kconfig?
> > You can just wrap the call snd_hdac_ext_bus_init() with #if/endif,
> > e.g. in soc/sof/intel/hda.h,
> >
> > static inline void sof_hda_bus_init(struct hdac_bus *bus, struct device *dev,
> > 				    const struct hdac_ext_bus_ops *ext_ops)
> > {
> > #if IS_ENABLED(CONFIG_SND_SOC_SOF_HDA)
> > 	snd_hdac_ext_bus_init(bus, dev, NULL, NULL, ext_ops);
> > #endif
> > }
> 
> We still need initializations for some of the data structures when
> SOF_HDA is not defined.

Which data structure?  The function above is only initializing the
given struct hdac_bus object.  I'm not suggesting to change the caller
site, hda_init() of sound/soc/sof/intel/hda.c.


thanks,

Takashi

  reply	other threads:[~2019-05-31 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 17:11 Why open-coding in sof_hda_bus_init()? Takashi Iwai
2019-05-31 17:43 ` Pierre-Louis Bossart
2019-05-31 18:22   ` Takashi Iwai
2019-05-31 18:31     ` Pierre-Louis Bossart
2019-05-31 19:06       ` Takashi Iwai [this message]
2019-05-31 19:44         ` Takashi Iwai
2019-05-31 20:23           ` Pierre-Louis Bossart
2019-05-31 20:36             ` Takashi Iwai
2019-05-31 20:59               ` Pierre-Louis Bossart
2019-05-31 21:20                 ` Takashi Iwai
2019-06-03  5:58                   ` Keyon Jie

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=s5hzhn2jvf2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=yang.jie@linux.intel.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.