From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
fntoth@gmail.com
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Hans de Goede <hdegoede@redhat.com>,
vkoul@kernel.org, Mark Brown <broonie@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [bug report] ASoC: Intel: mrfld - create separate module for pci part
Date: Fri, 3 Dec 2021 22:41:03 +0200 [thread overview]
Message-ID: <YaqA30mx4nUVdJoZ@smile.fi.intel.com> (raw)
In-Reply-To: <Yap/80NxtU0QLqo0@smile.fi.intel.com>
On Fri, Dec 03, 2021 at 10:37:07PM +0200, Andy Shevchenko wrote:
> On Fri, Dec 03, 2021 at 07:46:04AM -0600, Pierre-Louis Bossart wrote:
> > On 12/3/21 4:13 AM, Dan Carpenter wrote:
> > > Hello Vinod Koul,
> > >
> > > The patch f533a035e4da: "ASoC: Intel: mrfld - create separate module
> > > for pci part" from Nov 4, 2014, leads to the following Smatch static
> > > checker warning:
...
> > > Surely there should be a "return 0;" before the do_release_regions:
> > > label? How does this code work?
> >
> > Thanks for reporting this Dan. Yes this doesn't look good at all.
> >
> > This PCI part is only used on Merrifield/Tangier, and I am not sure if
> > anyone ever managed to make audio work with the upstream version of this
> > driver. It's my understanding that this platform is no longer maintained
> > by Intel, and the Edison Yocto code uses the SOF driver.
> >
> > The Kconfig updated in 2018 hints at those limitations:
> >
> > config SND_SST_ATOM_HIFI2_PLATFORM_PCI
> > tristate "PCI HiFi2 (Merrifield) Platforms"
> > depends on X86 && PCI
> > select SND_SST_ATOM_HIFI2_PLATFORM
> > help
> > If you have a Intel Merrifield/Edison platform, then
> > enable this option by saying Y or m. Distros will typically not
> > enable this option: while Merrifield/Edison can run a mainline
> > kernel with limited functionality it will require a firmware file
> > which is not in the standard firmware tree
> >
> > I would guess that indeed a return 0; is missing, but maybe it's time to
> > remove this PCI code completely. I can't think of any user of the PCI
> > parts of this driver.
> >
> > Andy, Hans, Mark, Takashi, what do you think?
>
> The Edison platform and actually some more based on Intel Merrifield are still
> alive and on the (second hand) market. But yes, I would rather focus on making
> SOF working there, but via PCI bus (or with ACPI, ASL code for which one should
> actually write down, currently it's a device with PCI interface only).
That said, Pierre, have you been able to setup your Edison to see anything on
I2S with SOF?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-03 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 10:13 [bug report] ASoC: Intel: mrfld - create separate module for pci part Dan Carpenter
2021-12-03 13:46 ` Pierre-Louis Bossart
2021-12-03 18:42 ` Mark Brown
2021-12-03 20:37 ` Andy Shevchenko
2021-12-03 20:41 ` Andy Shevchenko [this message]
2021-12-03 22:58 ` Pierre-Louis Bossart
2021-12-03 23:33 ` Ferry Toth
2021-12-03 20:39 ` Andy Shevchenko
2021-12-04 13:50 ` Hans de Goede
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=YaqA30mx4nUVdJoZ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=fntoth@gmail.com \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vkoul@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