All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 5/5] ASoC: mc13783: Add devicetree support
Date: Mon, 6 Jan 2014 13:28:41 +0000	[thread overview]
Message-ID: <20140106132841.GV31886@sirena.org.uk> (raw)
In-Reply-To: <1388907515-18975-5-git-send-email-shc_work@mail.ru>


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

On Sun, Jan 05, 2014 at 11:38:35AM +0400, Alexander Shiyan wrote:
> This patch adds devicetree support for mc13783-codec.
> Since we have not compatible string for this codec, just override
> of_node for allow using phandle of node in the DT.

All DT patches should be sent to the DT maintainers for review.

>  Documentation/devicetree/bindings/mfd/mc13xxx.txt |  4 +++-
>  drivers/mfd/mc13xxx-core.c                        | 12 +++++++-----
> 
Since this has MFD updates you also need to send it to the MFD
maintainers.

>  Optional properties:
>  - fsl,mc13xxx-uses-adc : Indicate the ADC is being used
> -- fsl,mc13xxx-uses-codec : Indicate the Audio Codec is being used

This is an incompatible binding change; deprecating is fine but it
should still be supported.  Is there not a default set of port
assignments that can be used?

> +	pdev->dev.of_node = of_find_node_by_name(pdev->dev.parent->of_node,
> +						 "codec");
> +

You shouldn't be messing with the of_node in the struct device, this is
managed by the driver model and setting one that wasn't added in sync
with everything else can introduce breakage.

> +	if (priv->adc_ssi_port != MC13783_SSI1_PORT &&
> +	    priv->adc_ssi_port != MC13783_SSI2_PORT)
> +		return -EINVAL;
> +	if (priv->dac_ssi_port != MC13783_SSI1_PORT &&
> +	    priv->dac_ssi_port != MC13783_SSI2_PORT)
> +		return -EINVAL;

What about DAC or ADC only systems?

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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



  reply	other threads:[~2014-01-06 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05  7:38 [PATCH 1/5] ASoC: mc13783: Use module_platform_driver_probe() Alexander Shiyan
2014-01-05  7:38 ` [PATCH 2/5] ASoC: mc13783: Use core error messages if registration fails Alexander Shiyan
2014-01-06 15:38   ` Mark Brown
2014-01-05  7:38 ` [PATCH 3/5] ASoC: mc13783: Drop fixed ADC & DAC ports usage Alexander Shiyan
2014-01-06 15:38   ` Mark Brown
2014-01-05  7:38 ` [PATCH 4/5] ASoC: mc13783: trivial: Cleanup module Alexander Shiyan
2014-01-06 15:38   ` Mark Brown
2014-01-05  7:38 ` [PATCH 5/5] ASoC: mc13783: Add devicetree support Alexander Shiyan
2014-01-06 13:28   ` Mark Brown [this message]
2014-01-06 13:46     ` Alexander Shiyan
2014-01-06 15:12       ` Mark Brown
2014-01-07  7:00         ` Alexander Shiyan
2014-01-07 11:08           ` Mark Brown
2014-01-06 15:38 ` [PATCH 1/5] ASoC: mc13783: Use module_platform_driver_probe() 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=20140106132841.GV31886@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=shc_work@mail.ru \
    --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.