mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Inha Song <ideal.song@samsung.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, sameo@linux.intel.com,
	ckeepax@opensource.wolonmicro.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: Re: [alsa-devel][PATCH 1/2] mfd: arizona: Add support for OUTn_MONO register control
Date: Thu, 18 Dec 2014 16:42:58 +0900	[thread overview]
Message-ID: <20141218164258.6785ca4e@songinha-Samsung-DeskTop-System> (raw)
In-Reply-To: <20141209085717.GT3951@x1>

Hi,
Sorry for the late reply.

On Tue, 09 Dec 2014 08:57:17 +0000
Lee Jones <lee.jones@linaro.org> wrote:

> On Mon, 08 Dec 2014, Inha Song wrote:
> 
> > Some boards need to set the OUTn_MONO register to configurates
> > the output signal path as a mono differential output. This
> > wlf,out-mono property is optional. If present, values must be
> > specified less than or equal to the number of output signals.
> > If values less than the number of output signals, elements
> > that has not been specified are set to 0 by default.
> > 
> > Example:
> >  - wlf,out-mono = <1 0 1>; /* set OUT1,OUT3 to mono differential */
> > 
> > Signed-off-by: Inha Song <ideal.song@samsung.com>
> > ---
> >  drivers/mfd/arizona-core.c | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
> > index bce7c07..117be32 100644
> > --- a/drivers/mfd/arizona-core.c
> > +++ b/drivers/mfd/arizona-core.c
> > @@ -561,6 +561,16 @@ static int arizona_of_get_core_pdata(struct arizona *arizona)
> >  		count++;
> >  	}
> >  
> > +	count = 0;
> > +	of_property_for_each_u32(arizona->dev->of_node, "wlf,out-mono", prop,
> > +				 cur, val) {
> 
> Nit: Can you break after the first parameter instead?
> 
> > +		if (count == ARRAY_SIZE(arizona->pdata.out_mono))
> 
> It's better practise to use ">=".

OK, I will fix this.

Best Regards,
Inha Song.

> 
> > +			break;
> > +
> > +		arizona->pdata.out_mono[count] = !!val;
> > +		count++;
> > +	}
> > +
> >  	return 0;
> >  }
> >  
> 
> -- 
> Lee Jones
> Linaro STMicroelectronics Landing Team Lead
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2014-12-18  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  9:20 [alsa-devel][PATCH 0/2] " Inha Song
2014-12-08  9:20 ` [alsa-devel][PATCH 1/2] " Inha Song
2014-12-09  8:57   ` Lee Jones
2014-12-18  7:42     ` Inha Song [this message]
2014-12-08  9:20 ` [alsa-devel][PATCH 2/2] mfd: arizona: Update DT binding to support OUTn_MONO init_data Inha Song

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=20141218164258.6785ca4e@songinha-Samsung-DeskTop-System \
    --to=ideal.song@samsung.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolonmicro.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®