All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Hans de Goede <hdegoede@redhat.com>,
	alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: ASoC: Intel: sst: Missing IRQ at index 5 on BYT-T device
Date: Wed, 9 Jan 2019 19:22:41 +0000	[thread overview]
Message-ID: <20190109192241.GN10405@sirena.org.uk> (raw)
In-Reply-To: <20181217180330.GA845@gerhold.net>


[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]

On Mon, Dec 17, 2018 at 07:03:31PM +0100, Stephan Gerhold wrote:

> Side note:
> I have considered fixing this in the DSDT table a few times before but 
> have never tried it because it kind of feels wrong to me. It would 
> probably work, but I believe the kernel is at fault here:

> I've been fixing mistakes and adding missing GPIOs to the DSDT, but is 
> this really the case here? Everything that is needed for the driver 
> exists in the ACPI table. If this was a BYT-CR device, it would work 
> as-is, with no additional modifications.

> Now, in order to fulfill the current expectations for BYT-T devices,
> I would need to add 4 additional IRQs that would never be used.
> But which IRQs would I list there? Dummy/invalid IRQs? To me, that
> does not sound like the DSDT will become any more valid.

> Let me know what you think! :)

This thread appears to have died without a conclusion I can see?  I
don't have strong feelings here, it seems like it's a choice between
different evils so people working on the platform should make the call.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2019-01-09 19:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 18:54 ASoC: Intel: sst: Missing IRQ at index 5 on BYT-T device Stephan Gerhold
2018-12-16 19:07 ` Hans de Goede
2018-12-16 22:03   ` Antonio Ospite
2018-12-17  7:53     ` Hans de Goede
2018-12-17  8:25       ` Antonio Ospite
2018-12-17 18:03   ` Stephan Gerhold
2019-01-09 19:22     ` Mark Brown [this message]
2019-01-09 21:10       ` Pierre-Louis Bossart
2019-01-09 21:14         ` Mark Brown
2018-12-17 14:52 ` Pierre-Louis Bossart
2018-12-17 18:17   ` Stephan Gerhold
2018-12-17 18:29     ` Pierre-Louis Bossart
2018-12-17 19:10       ` Stephan Gerhold
2018-12-17 19:39         ` Pierre-Louis Bossart
2018-12-17 20:32           ` Stephan Gerhold
2018-12-17 20:43             ` Stephan Gerhold
2018-12-18  2:13               ` Pierre-Louis Bossart
2018-12-19 13:07                 ` Stephan Gerhold
2018-12-19 14:04                   ` Pierre-Louis Bossart
2018-12-19 14:23                     ` Hans de Goede
2018-12-19 20:59                       ` Antonio Ospite
2018-12-19 21:51                         ` Hans de Goede
2018-12-19 15:01                     ` Stephan Gerhold
2018-12-19 16:54                       ` Pierre-Louis Bossart
2018-12-19 17:35                         ` Stephan Gerhold
2018-12-19 20:56                           ` Antonio Ospite
2019-01-03 10:04                             ` Antonio Ospite

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=20190109192241.GN10405@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=hdegoede@redhat.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=stephan@gerhold.net \
    --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 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.