public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Support Opensource <Support.Opensource@diasemi.com>,
	Sathyanarayana Nujella <sathyanarayana.nujella@intel.com>
Subject: Re: [PATCH 2/3] ASoC: da7219: Add ACPI parsing support
Date: Fri, 6 May 2016 17:42:08 +0100	[thread overview]
Message-ID: <20160506164208.GV6292@sirena.org.uk> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A0337D463C303@SW-EX-MBX01.diasemi.com>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On Fri, May 06, 2016 at 02:45:00PM +0000, Opensource [Adam Thomson] wrote:
> On May 06, 2016, 13:39, Mark Brown wrote:

> > > -	/* Handle any DT/platform data */
> > > -	if ((codec->dev->of_node) && (da7219->pdata))
> > > +	/* Handle any DT/ACPI/platform data */
> > > +	if (((codec->dev->of_node) || is_acpi_node(codec->dev->fwnode)) &&
> > > +	    (da7219->pdata))
> > >  		da7219->pdata->aad_pdata = da7219_aad_of_to_pdata(codec);

> > >  	da7219_aad_handle_pdata(codec);

> > Surely we should be able to check if there's firmware data without
> > enumerating every possible firmware type?

> There doesn't seem to be a unified check for this. Also, Given these are the
> only two types the driver expects and supports right now, I don't see a problem
> being explicit here in the checking.

Again it's pointing out something that looks like it's missing from the
fwnode API - if people are supposed to be able to write firmware neutral
drivers they should be able to do everything they need at the fwnode
level.

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

  reply	other threads:[~2016-05-06 16:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 10:53 [PATCH 0/3] ASoC: da7219: Add ACPI initialisation support to driver Adam Thomson
2016-05-05 10:53 ` [PATCH 1/3] ASoC: da7219: Convert driver to use generic device/fwnode functions Adam Thomson
2016-05-06 12:26   ` Mark Brown
2016-05-06 14:33     ` Opensource [Adam Thomson]
2016-05-06 16:05       ` Mark Brown
2016-05-09 12:05         ` Opensource [Adam Thomson]
2016-05-09 14:56           ` Mark Brown
2016-05-05 10:53 ` [PATCH 2/3] ASoC: da7219: Add ACPI parsing support Adam Thomson
2016-05-06 12:39   ` Mark Brown
2016-05-06 14:45     ` Opensource [Adam Thomson]
2016-05-06 16:42       ` Mark Brown [this message]
2016-05-05 10:53 ` [PATCH 3/3] ASoC: da7219: Add initial ACPI id for device Adam Thomson
2016-06-10 10:18 ` [PATCH 0/3] ASoC: da7219: Add ACPI initialisation support to driver Opensource [Adam Thomson]

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=20160506164208.GV6292@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sathyanarayana.nujella@intel.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox