From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Kirill Esipov <yesipov@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] rtc: ds3232: add temperature support
Date: Tue, 27 Jun 2017 15:00:57 +0200 [thread overview]
Message-ID: <20170627130057.yhhalp2epmmdicz7@piout.net> (raw)
In-Reply-To: <CAJcpCzF1SJ2v-KsJXN7c=BogeQv4LdAZEgZFsgVVy3HKPCcO1Q@mail.gmail.com>
On 27/06/2017 at 15:24:57 +0300, Kirill Esipov wrote:
> 2017-06-25 19:39 GMT+03:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
> > On Thu, Jun 22, 2017 at 7:58 PM, Kirill Esipov <yesipov@gmail.com> wrote:
> >> DS3232/DS3234 has the temperature registers with a resolution of 0.25
> >> degree celsius. This enables to get the value through hwmon.
> >>
> >> # cat /sys/class/hwmon/hwmon0/temp1_input
> >> 37250
> >
> >> +config RTC_DRV_DS3232_HWMON
> >> + bool "HWMON support for Dallas/Maxim DS3232/DS3234"
> >
> >> + depends on RTC_DRV_DS3232 && HWMON
> >> + depends on !(RTC_DRV_DS3232=y && HWMON=m)
> >
> > Perhaps it might be squeezed into one line (something like that logic
> > has been required by I2C related PMIC IIRC)
> >
> >> + default y
> >
> > Is it really sane default?
> >
>
> At first sight i thought that yes it is sane default (and others RTC with
> hwmon set it "default y" (ds1307, rv3029c2)).
> But if it's not sane, then we should turn it off by default in others drivers?
>
It is definitively sane.
>
> >> +#ifdef CONFIG_RTC_DRV_DS3232_HWMON
> >
> > IS_BUILTIN() ?
> >
I'd use IS_ENABLED in that case.
> >> +static int ds3232_hwmon_read_temp(struct device *dev, long int *mC)
> >> +{
> >> + struct ds3232 *ds3232 = dev_get_drvdata(dev);
> >> + u8 temp_buf[2];
> >> + s16 temp;
> >> + int ret;
> >> +
> >> + ret = regmap_bulk_read(ds3232->regmap, DS3232_REG_TEMPERATURE, temp_buf,
> >> + sizeof(temp_buf));
> >
> >> +
> >
> > Remove.
I'd recommend running checkpatch.pl --strict to remove the remaining
whitespace issues too (a few alignments are off).
> >
> > I dunno which style is preferred, though you may use
> > if (IS_BUILTIN(...))
> > return;
> >
> > at the beginning of the function and allow gcc optimizer to take care
> > of everything else.
> >
I don't have a strong opinion there.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-27 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 16:58 [PATCH v2] rtc: ds3232: add temperature support Kirill Esipov
2017-06-25 16:39 ` Andy Shevchenko
2017-06-27 12:24 ` Kirill Esipov
2017-06-27 13:00 ` Alexandre Belloni [this message]
2017-06-27 15:27 ` Kirill Esipov
2017-06-27 18:01 ` Alexandre Belloni
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=20170627130057.yhhalp2epmmdicz7@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=yesipov@gmail.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