From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Inha Song <ideal.song@samsung.com>,
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.wolfsonmicro.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [alsa-devel] [PATCH v2 RESEND 2/2] mfd: arizona: Update DT binding to support OUTn_MONO init_data
Date: Tue, 20 Jan 2015 16:02:48 +0000 [thread overview]
Message-ID: <20150120160248.GK13701@x1> (raw)
In-Reply-To: <20150120132001.GA21293@sirena.org.uk>
On Tue, 20 Jan 2015, Mark Brown wrote:
> On Tue, Jan 20, 2015 at 12:20:05PM +0000, Lee Jones wrote:
> > On Fri, 02 Jan 2015, Inha Song wrote:
>
> > > This patch update DT binding to support OUTn_MONO init_data. Each
> > > output signal can be configurated as a mono differential output.
> > > The mono differential configuration is selected using the OUTn_MONO
> > > registers.
>
> > This requires a DT Ack and an entry in the example.
>
> The DT maintainers have said they're OK with maintainers just merging
> things if they're comfortable with it (see the bindings specific
> submitting-patches.txt) and given their workload and general resulting
> responsiveness it's going to make it difficult go get anything done.
I only tend to poke the DT guys when I am unsure of something in the
binding. In this case it was a doubt whether we should be encoding
register values inside a property like this.
I would also be happy to take it with your Ack if you're happy with
it?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-01-20 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 8:03 [alsa-devel] [PATCH v2 RESEND 0/2] mfd: arizona: Add support for OUTn_MONO register control Inha Song
[not found] ` <1420185829-24886-1-git-send-email-ideal.song-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-02 8:03 ` [alsa-devel] [PATCH v2 RESEND 1/2] " Inha Song
[not found] ` <1420185829-24886-2-git-send-email-ideal.song-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-06 9:17 ` Charles Keepax
2015-01-20 12:20 ` Lee Jones
2015-01-20 15:46 ` Charles Keepax
2015-01-02 8:03 ` [alsa-devel] [PATCH v2 RESEND 2/2] mfd: arizona: Update DT binding to support OUTn_MONO init_data Inha Song
[not found] ` <1420185829-24886-3-git-send-email-ideal.song-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-01-06 9:17 ` Charles Keepax
2015-01-20 12:20 ` Lee Jones
2015-01-20 13:20 ` Mark Brown
2015-01-20 16:02 ` Lee Jones [this message]
2015-01-20 16:44 ` Charles Keepax
2015-01-20 16:57 ` Lee Jones
2015-01-20 15:49 ` Charles Keepax
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=20150120160248.GK13701@x1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ideal.song@samsung.com \
--cc=ijc+devicetree@hellion.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).