Linux RTC
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Michael Büsch" <m@bues.ch>
Cc: Gregory Hermant <gregory.hermant@calao-systems.com>,
	rtc-linux@googlegroups.com
Subject: Re: [rtc-linux] rv3029 EEPROM handling
Date: Mon, 29 Feb 2016 20:52:58 +0100	[thread overview]
Message-ID: <20160229195258.GB2627@piout.net> (raw)
In-Reply-To: <20160229180749.42f75ec8@wiggum>

On 29/02/2016 at 18:07:49 +0100, Michael B=C3=BCsch wrote :
> > Also, to export the temperature, use hwmon, see:
> > http://git.kernel.org/cgit/linux/kernel/git/abelloni/linux.git/commit/?=
h=3Drtc-next&id=3D445c02076f1e60d2ee51503bf1288ef9f3bc8809
>=20
> That is a rather weird API.
> Is there a special naming scheme required for the attribute?
> What does the 'input' mean in 'temp1_input'? And why is it temp1
> instead of temp0?

It means that you can read the value as opposed to output it for example
on a 3d printing nozzle.

I'm not sure why it is indexed starting with 1 but probably because
usually that's how user documentation is written. You'd have to ask the
hwmon maintainers ;)

>=20
> > You may want to use regmap instead of defining your own update_bits
> > (rv3029c2_i2c_maskset_reg) but that is a more invasie change that you
> > may leave out for now.
>=20
> Ok, I will do this last.
> Don't hold your breath. :)
>=20

I'm not even sure this is a good idea but I'd need to have a look at the
code to know ;)


--=20
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

--=20
--=20
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---=20
You received this message because you are subscribed to the Google Groups "=
rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2016-02-29 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 14:39 [rtc-linux] rv3029 EEPROM handling Michael Büsch
2016-02-28  0:31 ` Alexandre Belloni
2016-02-28  8:44   ` Michael Büsch
2016-02-28 10:41     ` Alexandre Belloni
2016-02-28 11:58       ` Michael Büsch
2016-02-28 12:36         ` Alexandre Belloni
2016-02-28 17:14           ` Michael Büsch
2016-02-28 21:39             ` Alexandre Belloni
2016-02-29 17:07               ` Michael Büsch
2016-02-29 19:52                 ` Alexandre Belloni [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=20160229195258.GB2627@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=gregory.hermant@calao-systems.com \
    --cc=m@bues.ch \
    --cc=rtc-linux@googlegroups.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