All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [PATCH 0/4] ASoC: Intel: fix kernel oops in machine drivers
Date: Tue,  4 Jun 2019 15:08:54 -0500	[thread overview]
Message-ID: <20190604200858.4867-1-pierre-louis.bossart@linux.intel.com> (raw)

The changes made for v5.1 to override the default platform_name
assumed the card device was properly initialized so that devm_strdup()
could be used. This is true for the majority of the machine drivers,
but unfortunately this isn't valid for four of the Cherrytrail-based
ones which don't follow the same programming flow and initialize the
card device last. After hitting a kernel oops on cht-bsw-max98090
(Cyan Chromebook) I found 3 other cases where the same fix is
required.

These fixes should be applied for 5.1 and 5.2. While it's not an
excuse for this miss, the impact is limited in that the kernel oops
will only happen when SOF is used.

Pierre-Louis Bossart (4):
  ASoC: Intel: cht_bsw_max98090: fix kernel oops with platform_name
    override
  ASoC: Intel: bytcht_es8316: fix kernel oops with platform_name
    override
  ASoC: Intel: cht_bsw_nau8824: fix kernel oops with platform_name
    override
  ASoC: Intel: cht_bsw_rt5672: fix kernel oops with platform_name
    override

 sound/soc/intel/boards/bytcht_es8316.c       | 2 +-
 sound/soc/intel/boards/cht_bsw_max98090_ti.c | 2 +-
 sound/soc/intel/boards/cht_bsw_nau8824.c     | 2 +-
 sound/soc/intel/boards/cht_bsw_rt5672.c      | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-06-04 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 20:08 Pierre-Louis Bossart [this message]
2019-06-04 20:08 ` [PATCH 1/4] ASoC: Intel: cht_bsw_max98090: fix kernel oops with platform_name override Pierre-Louis Bossart
2019-06-06 21:27   ` Applied "ASoC: Intel: cht_bsw_max98090: fix kernel oops with platform_name override" to the asoc tree Mark Brown
2019-06-04 20:08 ` [PATCH 2/4] ASoC: Intel: bytcht_es8316: fix kernel oops with platform_name override Pierre-Louis Bossart
2019-06-06 21:27   ` Applied "ASoC: Intel: bytcht_es8316: fix kernel oops with platform_name override" to the asoc tree Mark Brown
2019-06-04 20:08 ` [PATCH 3/4] ASoC: Intel: cht_bsw_nau8824: fix kernel oops with platform_name override Pierre-Louis Bossart
2019-06-06 21:27   ` Applied "ASoC: Intel: cht_bsw_nau8824: fix kernel oops with platform_name override" to the asoc tree Mark Brown
2019-06-04 20:08 ` [PATCH 4/4] ASoC: Intel: cht_bsw_rt5672: fix kernel oops with platform_name override Pierre-Louis Bossart
2019-06-06 21:27   ` Applied "ASoC: Intel: cht_bsw_rt5672: fix kernel oops with platform_name override" to the asoc tree Mark Brown

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=20190604200858.4867-1-pierre-louis.bossart@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=tiwai@suse.de \
    /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.