From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-omap@vger.kernel.org
Subject: Pandora audio using machine_is_omap3_pandora() check
Date: Mon, 27 Jun 2022 12:52:25 +0300 [thread overview]
Message-ID: <Yrl92RILZwhQOP+e@atomide.com> (raw)
Hi Grazvydas,
Arnd noticed that pandora audio is using machine_is_omap3_pandora() check
that never succeeds for devicetree booting machines. Looks like this has
been broken at some point many years ago with the devicetree conversion.
Does anybody have an interest in fixing this driver?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Pandora audio using machine_is_omap3_pandora() check
Date: Mon, 27 Jun 2022 12:52:25 +0300 [thread overview]
Message-ID: <Yrl92RILZwhQOP+e@atomide.com> (raw)
Hi Grazvydas,
Arnd noticed that pandora audio is using machine_is_omap3_pandora() check
that never succeeds for devicetree booting machines. Looks like this has
been broken at some point many years ago with the devicetree conversion.
Does anybody have an interest in fixing this driver?
Regards,
Tony
next reply other threads:[~2022-06-27 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:52 Tony Lindgren [this message]
2022-06-27 9:52 ` Pandora audio using machine_is_omap3_pandora() check Tony Lindgren
2022-06-27 11:40 ` H. Nikolaus Schaller
2022-06-27 11:40 ` H. Nikolaus Schaller
2022-06-27 13:53 ` Tony Lindgren
2022-06-27 13:53 ` Tony Lindgren
2022-07-05 21:39 ` Stefan Leichter
2022-07-11 10:05 ` H. Nikolaus Schaller
2022-07-11 10:05 ` H. Nikolaus Schaller
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=Yrl92RILZwhQOP+e@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=hns@goldelico.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@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.