alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Curtis Malainey <cujomalainey@google.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Ben Zhang <benzh@chromium.org>,
	Jie Yang <yang.jie@linux.intel.com>,
	Takashi Iwai <tiwai@suse.com>,
	Pan Xiuli <xiuli.pan@linux.intel.com>,
	ALSA development <alsa-devel@alsa-project.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Alexios Zavras <alexios.zavras@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Curtis Malainey <cujomalainey@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [alsa-devel] [PATCH] ASoC: bdw-rt5677: add spi driver compile switches
Date: Mon, 6 Jan 2020 12:27:35 -0800	[thread overview]
Message-ID: <CAOReqxio6Y6uDaa1fPnFTwm+5ynNk92ibYY8UT_PCsfJJUEJeA@mail.gmail.com> (raw)
In-Reply-To: <f7420fdd-2591-225e-55e4-34e69ac5292c@linux.intel.com>

On Fri, Jan 3, 2020 at 6:29 PM Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
>
>
>
> On 1/3/20 5:34 PM, Curtis Malainey wrote:
> > If the SPI driver is not compiled in then the RT5677_SPI driver will not
> > be included as well which will cause the bdw-rt5677 driver to fail to
> > probe since the DSP components are managed by the RT5677_SPI driver. The
> > solution is to remove them when the driver is not present as part of the
> > build.
>
> it should be the other way around, this machine driver should have a
> dependency on SPI and select RT5677_SPI?
>
> That said, even with this fix, I still see issues, somehow the
> spi-RT5677AA component does not probe/register, see
> https://github.com/thesofproject/linux/pull/1659
>
> There must be an additional issue with SPI support here.
>
Good point, we should select the dependencies. I commented on your bug
as to what the issue might be.
> >
> > Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
> > Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> > CC: Pan Xiuli <xiuli.pan@linux.intel.com>
> > ---
> >   sound/soc/intel/boards/bdw-rt5677.c | 4 ++++
> >   1 file changed, 4 insertions(+)
> >
> > diff --git a/sound/soc/intel/boards/bdw-rt5677.c b/sound/soc/intel/boards/bdw-rt5677.c
> > index 2af8e5a62da84..d5ded2c545d2c 100644
> > --- a/sound/soc/intel/boards/bdw-rt5677.c
> > +++ b/sound/soc/intel/boards/bdw-rt5677.c
> > @@ -74,11 +74,13 @@ static const struct snd_soc_dapm_route bdw_rt5677_map[] = {
> >       /* CODEC BE connections */
> >       {"SSP0 CODEC IN", NULL, "AIF1 Capture"},
> >       {"AIF1 Playback", NULL, "SSP0 CODEC OUT"},
> > +#if IS_ENABLED(CONFIG_SND_SOC_RT5677_SPI)
> >       {"DSP Capture", NULL, "DSP Buffer"},
> >
> >       /* DSP Clock Connections */
> >       { "DSP Buffer", NULL, "SSP0 CODEC IN" },
> >       { "SSP0 CODEC IN", NULL, "DSPTX" },
> > +#endif
> >   };
> >
> >   static const struct snd_kcontrol_new bdw_rt5677_controls[] = {
> > @@ -319,6 +321,7 @@ static struct snd_soc_dai_link bdw_rt5677_dais[] = {
> >               SND_SOC_DAILINK_REG(fe, dummy, platform),
> >       },
> >
> > +#if IS_ENABLED(CONFIG_SND_SOC_RT5677_SPI)
> >       /* Non-DPCM links */
> >       {
> >               .name = "Codec DSP",
> > @@ -326,6 +329,7 @@ static struct snd_soc_dai_link bdw_rt5677_dais[] = {
> >               .ops = &bdw_rt5677_dsp_ops,
> >               SND_SOC_DAILINK_REG(dsp),
> >       },
> > +#endif
> >
> >       /* Back End DAI links */
> >       {
> >
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2020-01-06 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 23:34 [alsa-devel] [PATCH] ASoC: bdw-rt5677: add spi driver compile switches Curtis Malainey
2020-01-04  2:29 ` Pierre-Louis Bossart
2020-01-06 20:27   ` Curtis Malainey [this message]

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=CAOReqxio6Y6uDaa1fPnFTwm+5ynNk92ibYY8UT_PCsfJJUEJeA@mail.gmail.com \
    --to=cujomalainey@google.com \
    --cc=alexios.zavras@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=benzh@chromium.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=cujomalainey@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=xiuli.pan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).