From: Felipe Balbi <balbi@ti.com>
To: Michael Welling <mwelling@ieee.org>
Cc: Felipe Balbi <balbi@ti.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
<pmeerw@pmeerw.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] iio: light: add support for TI's opt3001 light sensor
Date: Mon, 29 Sep 2014 13:53:25 -0500 [thread overview]
Message-ID: <20140929185325.GA1939@saruman> (raw)
In-Reply-To: <20140929183856.GA11871@sysresccd>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Hi,
On Mon, Sep 29, 2014 at 01:38:56PM -0500, Michael Welling wrote:
> On Mon, Sep 29, 2014 at 09:02:27AM -0500, Felipe Balbi wrote:
> > Alright, this is already ridiculous. Andrew, if I resend the patch can
> > you apply it since maintainer has been ignoring this thread anyway ?
> >
>
> Do you reall think this is the best way to approach this?
when maintainer doesn't respond for weeks, yeah! Sure it is.
> Perhaps it would be better to explain what each field of the
> configuration register does and then we can move on.
perhaps Jonathan could tell me exactly what he wants because I can't
handle back-and-forth anymore. Specially when he complains about stuff
he asked me to modify himself.
> In particular the OPT3001_CONFIGURATION_L field needs to be explained
> such that the ABI can be properly applied.
>
> Looking at the docs for the Windows demo program the field is associated
> with a latch configuration. What does this bit field actually do?
>
> Either have TI release the documentation or add comments to each of the
> fields of each of the registers such that we can understand what exactly
> they are doing.
TI will release the documentation when that's all cleared up with Legal.
You can't expect it to be any earlier than that.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-29 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140915052137.GA11866@saruman.home>
[not found] ` <20140916170316.GD19010@saruman.home>
[not found] ` <20140917150041.GA6903@saruman.home>
[not found] ` <20140918133631.GA24847@saruman.home>
[not found] ` <20140919162129.GE26946@saruman.home>
[not found] ` <20140922140914.GC25620@saruman>
[not found] ` <20140923140924.GA28592@saruman>
[not found] ` <20140924143610.GA17997@saruman>
[not found] ` <20140925221619.GA10644@saruman>
[not found] ` <20140927041959.GA28445@saruman>
2014-09-29 14:02 ` [RESEND PATCH] iio: light: add support for TI's opt3001 light sensor Felipe Balbi
2014-09-29 17:14 ` Jonathan Cameron
2014-09-29 18:38 ` Michael Welling
2014-09-29 18:53 ` Felipe Balbi [this message]
2014-09-29 19:07 ` Daniel Baluta
2014-09-29 19:45 ` Felipe Balbi
2014-09-29 22:38 ` Michael Welling
2014-09-29 22:46 ` Felipe Balbi
2014-09-29 23:41 ` Michael Welling
2014-09-30 21:22 ` Felipe Balbi
2014-10-02 18:05 ` Felipe Balbi
2014-10-04 3:17 ` Michael Welling
2014-10-04 9:43 ` Jonathan Cameron
2014-10-06 19:54 ` Felipe Balbi
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=20140929185325.GA1939@saruman \
--to=balbi@ti.com \
--cc=akpm@linux-foundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwelling@ieee.org \
--cc=pmeerw@pmeerw.net \
/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).