From: Tom Levens <tom.levens-vJEk5272eHo@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: Tom Levens <tom.levens-vJEk5272eHo@public.gmane.org>,
Mike Looijmans <mike.looijmans-Oq418RWZeHk@public.gmane.org>,
jdelvare-IBi9RG/b67k@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-hwmon-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 3/3] hwmon: ltc2990: support all measurement modes
Date: Wed, 28 Jun 2017 19:02:29 +0200 [thread overview]
Message-ID: <alpine.LRH.2.20.1706281819540.21032@lxplus028.cern.ch> (raw)
In-Reply-To: <20170628160048.GA8915-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
On Wed, 28 Jun 2017, Guenter Roeck wrote:
> 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
>
You are right, there was still an open question about how best to handle
the mode selection in DT.
In the latest version of my patch I have it implemented as an array for
setting the two values, for example:
lltc,meas-mode = <7 3>;
This sets bits [2..0] = 7 and [4..3] = 3. Of course these could be split
into two DT properties, but I was unsure what to name them as both fields
are called "mode" in the datasheet and "mode-43"/"mode-20" (or similar) is
ugly.
With regards to your proposal, it is not clear to me whether the modes
which have the same result are exactly equivalent. Does disabling a
measurement with the mode[4..3] bits really leaves the part in a safe
state for all possible HW connections? With this doubt in my head, I would
prefer to keep the option available to the user to select any specific
mode. But I am open to suggestions.
Mike, if you would like to test it, the latest version of my code is here:
https://github.com/levens/ltc2990/blob/dev/drivers/hwmon/ltc2990.c
Cheers,
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-28 17:02 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
[not found] ` <1479384616-12479-2-git-send-email-tom.levens-vJEk5272eHo@public.gmane.org>
2016-11-18 14:50 ` Rob Herring
2016-11-18 15:36 ` Tom Levens
[not found] ` <1479384616-12479-1-git-send-email-tom.levens-vJEk5272eHo@public.gmane.org>
2016-11-17 12:10 ` [PATCH v2 3/3] hwmon: ltc2990: support all measurement modes Tom Levens
[not found] ` <1479384616-12479-3-git-send-email-tom.levens-vJEk5272eHo@public.gmane.org>
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
[not found] ` <20161117234024.GA26747-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-11-18 12:23 ` Tom Levens
2016-11-18 14:16 ` Guenter Roeck
[not found] ` <410de6c9-a13e-51f7-4d66-6f4e2537c574-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-06-28 14:24 ` Mike Looijmans
2017-06-28 15:01 ` Guenter Roeck
[not found] ` <20170628150130.GC30968-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-06-28 15:29 ` Tom Levens
2017-06-28 16:00 ` Guenter Roeck
[not found] ` <20170628160048.GA8915-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-06-28 17:02 ` Tom Levens [this message]
2017-06-28 17:33 ` Mike Looijmans
[not found] ` <abe96add-88fc-af6c-a5ed-330c7ae422b9-Oq418RWZeHk@public.gmane.org>
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=alpine.LRH.2.20.1706281819540.21032@lxplus028.cern.ch \
--to=tom.levens-vjek5272eho@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jdelvare-IBi9RG/b67k@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-hwmon-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mike.looijmans-Oq418RWZeHk@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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).