Dne 08. 09. 20 v 10:19 Takashi Iwai napsal(a):
On Tue, 08 Sep 2020 03:47:46 +0200, Liao, Bard wrote:
-----Original Message----- From: Sound-open-firmware <sound-open-firmware-bounces@alsa- project.org> On Behalf Of Takashi Iwai Sent: Tuesday, September 8, 2020 2:59 AM To: sound-open-firmware@alsa-project.org Subject: [Sound-open-firmware] A branch can be used as to-be-upstreamed?
Hi,
as we got a bug report about the new Dell laptop with SoundWire audio, I tried to build a kernel with the downstream SOF patches, then I noticed that it's not so trivial to get the patches from SOF git tree that are applicable on top of upstream (either sound or Linus) tree.
Do we have a branch that may contain clean commits on top of the recent upstream? That is, a branch that is regularly rebased, so that each commit can be retrieved as a patch. Such a branch will make upstream submission easier, and it makes easier for distros to take the downstream patches, too.
Yes, please see the topic/sof-dev-rebase branch. https://github.com/thesofproject/linux/commits/topic/sof-dev-rebase
Thanks, that's it!
It seems that the missing patches to get things working in upstream for Intel soundwire hardware are:
[1] https://lore.kernel.org/alsa-devel/20200817222340.18042-1-yung-chuan.liao@li... [2] https://lore.kernel.org/alsa-devel/20200818140656.29014-1-yung-chuan.liao@li... [3] https://github.com/thesofproject/linux/commit/d1373fea0133d45c9e525fb47b1aa4...
The [2] is probably optional, but the syslog is flooded with parity errors for the Realtek codecs.
The patches should be applied top of the latest soundwire / asoc repos.
Jaroslav