From: Felipe Balbi <balbi@ti.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Michael Welling <mwelling@ieee.org>, Felipe Balbi <balbi@ti.com>,
Andrew Morton <akpm@linux-foundation.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, 6 Oct 2014 14:54:31 -0500 [thread overview]
Message-ID: <20141006195431.GD17445@saruman> (raw)
In-Reply-To: <542FC15D.3070503@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]
On Sat, Oct 04, 2014 at 10:43:57AM +0100, Jonathan Cameron wrote:
> On 04/10/14 04:17, Michael Welling wrote:
> > On Thu, Oct 02, 2014 at 01:05:53PM -0500, Felipe Balbi wrote:
> >> Hi,
> >>
> >> On Tue, Sep 30, 2014 at 04:22:04PM -0500, Felipe Balbi wrote:
> >>> On Mon, Sep 29, 2014 at 06:41:59PM -0500, Michael Welling wrote:
> >>>> On Mon, Sep 29, 2014 at 05:46:38PM -0500, Felipe Balbi wrote:
> >>>>> Hi,
> >>>>>
> >>>>> On Mon, Sep 29, 2014 at 05:38:33PM -0500, Michael Welling 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?
> >>>>>>
> >>>>>> Still no technical information. Without all the facts how can you expect
> >>>>>> him to tell you what he wants?
> >>>>>
> >>>>> yeah, because clearly he doesn't know himself, right ?
> >>>>
> >>>> Could you explain how it works to me then?
> >>>
> >>> checking how much of the docs I can expose now, gimme a couple days.
> >>
> >> alright, here's a snippet of what's on preliminary docs:
> >>
> Firstly, thanks Felipe for going through the process to get permission
> to release the snippets. I know this can be a real pain to do.
alright, np. Device will be launched soonish, so full datasheet should
be in TI's website in the coming weeks or so.
I'll wait until v3.18-rc1 is tagged before working on this again.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-10-06 19:54 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
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 [this message]
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=20141006195431.GD17445@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).