From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Steffen Trumtrar <s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Alessandro Zummo
<a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org>,
Alexandre Belloni
<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: Re: [PATCH v3 2/2] rtc: add driver for RX6110SA real time clock
Date: Tue, 08 Dec 2015 11:30:21 +0100 [thread overview]
Message-ID: <1449570621.18374.1.camel@pengutronix.de> (raw)
In-Reply-To: <1449568461-26016-2-git-send-email-s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Am Dienstag, den 08.12.2015, 10:54 +0100 schrieb Steffen Trumtrar:
> The RX6110 comes in two different variants: SPI and I2C.
> This driver only supports the SPI variant.
>
> If the need ever arises to also support the I2C variant, this driver
> could easily be refactored to support both cases.
>
> Signed-off-by: Steffen Trumtrar <s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Reviewed-by: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
I have a few suggestions:
[...]
> diff --git a/drivers/rtc/rtc-rx6110.c b/drivers/rtc/rtc-rx6110.c
> new file mode 100644
> index 000000000000..aa9d89d5d2de
> --- /dev/null
> +++ b/drivers/rtc/rtc-rx6110.c
> @@ -0,0 +1,438 @@
> +/*
> + * Driver for the Epson RTC module RX-6110 SA
> + *
> + * Copyright(C) 2015 Pengutronix, Steffen Trumtrar <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> + * Copyright(C) SEIKO EPSON CORPORATION 2013. All rights reserved.
> + *
> + * This driver software is distributed as is, without any warranty of any kind,
> + * either express or implied as further specified in the GNU Public License.
> + * This software may be used and distributed according to the terms of the GNU
> + * Public License, version 2 as published by the Free Software Foundation.
> + * See the file COPYING in the main directory of this archive for more details.
> + *
> + * You should have received a copy of the GNU General Public License along with
> + * this program. If not, see <http://www.gnu.org/licenses/>.
> + */
> +
> +#include <linux/bcd.h>
> +#include <linux/init.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/of_device.h>
> +#include <linux/of_gpio.h>
I think these three can be dropped.
> +#include <linux/regmap.h>
> +#include <linux/rtc.h>
> +#include <linux/spi/spi.h>
> +
> +/* RX-6110 Register definitions */
[...]
> +
> +static struct spi_driver rx6110_driver;
Several drivers do this. Instead of the forward declaration and using
rx6110_driver.driver.name in devm_rtc_device_register below, why not
just have a #define RX6110_DRIVER_NAME "rx6110-rtc" and reuse that?
Actually, I think the "-rtc" suffix is superfluous in the rtc name.
I'd just use "rx6110" as a parameter to devm_rtc_device_register.
> +struct rx6110_data {
> + struct rtc_device *rtc;
> + struct regmap *regmap;
> +};
[...]
> +/**
> + * rx6110_init - initialize the rx6110 registers
> + *
> + * @rx6110: pointer to the rx6110 struct in use
> + *
> + */
> +static int rx6110_init(struct rx6110_data *rx6110)
> +{
> + struct rtc_device *rtc = rx6110->rtc;
> + int ext;
> + int flags;
> + int ctrl;
ctrl is unused, except in the dev_dbg to print 0 below.
> + int ret;
> +
> + /* set reserved register 0x17 with specified value of 0xB8 */
> + ret = regmap_write(rx6110->regmap, RX6110_REG_RES1, 0xB8);
> + if (ret)
> + return ret;
> +
> + /* set reserved register 0x30 with specified value of 0x00 */
> + ret = regmap_write(rx6110->regmap, RX6110_REG_RES2, 0x00);
> + if (ret)
> + return ret;
> +
> + /* set reserved register 0x31 with specified value of 0x10 */
> + ret = regmap_write(rx6110->regmap, RX6110_REG_RES3, 0x10);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(rx6110->regmap, RX6110_REG_IRQ, 0x0);
> + if (ret)
> + return ret;
Maybe combine those using regmap_multi_reg_write? Not sure if the
sequence can be reordered to also include the writes below.
> + ret = regmap_update_bits(rx6110->regmap, RX6110_REG_EXT,
> + RX6110_BIT_EXT_TE, 0);
> + if (ret)
> + return ret;
> +
> + /* get current extension, flag, control register values */
> + ret = regmap_read(rx6110->regmap, RX6110_REG_EXT, &ext);
> + if (ret)
> + return ret;
> +
> + ret = regmap_read(rx6110->regmap, RX6110_REG_FLAG, &flags);
> + if (ret)
> + return ret;
> +
> + /* clear ctrl register */
> + ret = regmap_write(rx6110->regmap, RX6110_REG_CTRL, 0);
> + if (ret)
> + return ret;
> +
> + ctrl = 0;
This is unused ...
> + ret = regmap_write(rx6110->regmap, RX6110_REG_ALMIN, 0);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(rx6110->regmap, RX6110_REG_ALHOUR, 0);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(rx6110->regmap, RX6110_REG_ALWDAY, 0);
> + if (ret)
> + return ret;
> +
> + dev_dbg(&rtc->dev, "ext: %x, flag: %x, ctrl: %x\n", ext, flags, ctrl);
... except here.
> +
> + /* check for VLF Flag (set at power-on) */
> + if ((flags & RX6110_BIT_FLAG_VLF))
> + dev_warn(&rtc->dev, "Voltage low, data loss detected.\n");
> +
> + /* check for Alarm Flag */
> + if (flags & RX6110_BIT_FLAG_AF)
> + dev_warn(&rtc->dev, "An alarm may have been missed.\n");
> +
> + /* check for Periodic Timer Flag */
> + if (flags & RX6110_BIT_FLAG_TF)
> + dev_warn(&rtc->dev, "Periodic timer was detected\n");
> +
> + /* check for Update Timer Flag */
> + if (flags & RX6110_BIT_FLAG_UF)
> + dev_warn(&rtc->dev, "Update timer was detected\n");
> +
> + /* clear all flags BUT VLF */
> + ret = regmap_update_bits(rx6110->regmap, RX6110_REG_FLAG,
> + RX6110_BIT_FLAG_AF |
> + RX6110_BIT_FLAG_UF |
> + RX6110_BIT_FLAG_TF,
> + 0);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
[...]
> +/**
> + * rx6110_probe - initialize rtc driver
> + * @spi: pointer to spi device
> + */
> +static int rx6110_probe(struct spi_device *spi)
> +{
> + struct rx6110_data *rx6110;
> + int err;
> +
> + if ((spi->bits_per_word && spi->bits_per_word != 8)
> + || (spi->max_speed_hz > 2000000)
> + || (spi->mode != (SPI_CS_HIGH | SPI_CPOL | SPI_CPHA))) {
> + dev_warn(&spi->dev, "SPI settings: bits_per_word: %d, max_speed_hz: %d, mode: %xh\n",
> + spi->bits_per_word, spi->max_speed_hz, spi->mode);
> + dev_warn(&spi->dev, "driving device in an unsupported mode");
> + }
> +
> + rx6110 = devm_kzalloc(&spi->dev, sizeof(*rx6110), GFP_KERNEL);
> + if (!rx6110)
> + return -ENOMEM;
> +
> + rx6110->regmap = devm_regmap_init_spi(spi, ®map_spi_config);
> + if (IS_ERR(rx6110->regmap)) {
> + dev_err(&spi->dev, "regmap init failed for rtc rx6110\n");
Maybe print the error code.
> + return PTR_ERR(rx6110->regmap);
> + }
> +
> + spi_set_drvdata(spi, rx6110);
> +
> + rx6110->rtc = devm_rtc_device_register(&spi->dev,
> + rx6110_driver.driver.name,
That could be just "rx6110" instead of "rx6110-rtc" in my opinion.
> + &rx6110_rtc_ops, THIS_MODULE);
> +
> + if (IS_ERR(rx6110->rtc))
> + return PTR_ERR(rx6110->rtc);
> +
> + err = rx6110_init(rx6110);
> + if (err)
> + return err;
> +
> + rx6110->rtc->max_user_freq = 1;
> +
> + return 0;
> +}
regards
Philipp
--
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:[~2015-12-08 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 9:54 [PATCH v3 1/2] Documentation: devicetree: add epson rx6110 binding Steffen Trumtrar
[not found] ` <1449568461-26016-1-git-send-email-s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-12-08 9:54 ` [PATCH v3 2/2] rtc: add driver for RX6110SA real time clock Steffen Trumtrar
[not found] ` <1449568461-26016-2-git-send-email-s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-12-08 10:30 ` Philipp Zabel [this message]
[not found] ` <1449570621.18374.1.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-12-10 11:01 ` Steffen Trumtrar
2015-12-08 10:29 ` [PATCH v3 1/2] Documentation: devicetree: add epson rx6110 binding Philipp Zabel
[not found] ` <1449570566.3691.31.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-12-10 10:56 ` Steffen Trumtrar
2015-12-08 10:29 ` Philipp Zabel
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=1449570621.18374.1.camel@pengutronix.de \
--to=p.zabel-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org \
--cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@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).