mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Tom Levens <tom.levens@cern.ch>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	jdelvare@suse.com, robh+dt@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] hwmon: ltc2990: support all measurement modes
Date: Wed, 28 Jun 2017 09:00:48 -0700	[thread overview]
Message-ID: <20170628160048.GA8915@roeck-us.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1706281723170.31209@lxplus022.cern.ch>

On Wed, Jun 28, 2017 at 05:29:38PM +0200, Tom Levens wrote:
> 
[ ... ]

> >
> >>Whatever happened to this patch though? It didn't make it to mainline,
> >>otherwise I'd have found it sooner...
> >>
> >I'll have to look it up, but I guess I didn't get an updated version.
> 
> As far as I remember I had a working V3 of this patch, but it is entirely
> possible that it was never submitted as I have been busy with other projects
> recently. I'll dig it out and check that it is complete.
> 
FWIW, I don't see it at
https://patchwork.kernel.org/project/linux-hwmon/list/?submitter=171225&state=*

Maybe you were waiting for a reply from Rob. Either case, it might make
sense to only provide valid modes, ie to abstract the mode bits from the
hardware, such as

0 - internal temp only
1 - Tr1
2 - V1
3 - V1-V2
4 - Tr2
5 - V3
6 - V3-V4
7 to 14 - per bit 0..2

Guenter

  reply	other threads:[~2017-06-28 16:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 12:10 [PATCH v2 1/3] hwmon: ltc2990: refactor value conversion Tom Levens
2016-11-17 12:10 ` [PATCH v2 2/3] hwmon: ltc2990: add devicetree binding Tom Levens
2016-11-18 14:50   ` Rob Herring
2016-11-18 15:36     ` Tom Levens
2016-11-17 12:10 ` [PATCH v2 3/3] hwmon: ltc2990: support all measurement modes Tom Levens
2016-11-17 16:56   ` Guenter Roeck
2016-11-17 17:40     ` Mike Looijmans
2016-11-17 18:56       ` Guenter Roeck
2016-11-17 19:52         ` Mike Looijmans
2016-11-17 21:54           ` Guenter Roeck
2016-11-17 23:25             ` Tom Levens
2016-11-17 23:40               ` Guenter Roeck
2016-11-18 12:23                 ` Tom Levens
2016-11-18 14:16                   ` Guenter Roeck
2017-06-28 14:24     ` Mike Looijmans
2017-06-28 15:01       ` Guenter Roeck
2017-06-28 15:29         ` Tom Levens
2017-06-28 16:00           ` Guenter Roeck [this message]
2017-06-28 17:02             ` Tom Levens
2017-06-28 17:33               ` Mike Looijmans
2017-06-28 17:55                 ` Guenter Roeck
2017-06-29  7:45               ` Mike Looijmans
2017-06-29 11:46                 ` Tom Levens
2016-11-17 15:06 ` [PATCH v2 1/3] hwmon: ltc2990: refactor value conversion Guenter Roeck
2016-11-17 16:23   ` Tom Levens
2016-11-17 16:36     ` Guenter Roeck
2016-11-18  8:18       ` Tom Levens
2016-11-18 14:09         ` Guenter Roeck
2016-11-18 14:17           ` Guenter Roeck

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=20170628160048.GA8915@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.looijmans@topic.nl \
    --cc=robh+dt@kernel.org \
    --cc=tom.levens@cern.ch \
    /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

Powered by JetHome