devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: David Daney <david.daney@cavium.com>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v6] rtc: isl12026: Add driver.
Date: Fri, 2 Mar 2018 08:22:22 -0800	[thread overview]
Message-ID: <CAKjEs9FbNDKNs5j-aZAmHCYO1YE5g70vLyuk1hGDNvvRWj977w@mail.gmail.com> (raw)
In-Reply-To: <20180228151701.GM1479@piout.net>

[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]

I am no longer able to test this patch as I lost access to the hardware.

If someone else wants to take charge of the patch, that would be great.

Sorry I couldn't drive this to completion,
David Daney

On Wed, Feb 28, 2018 at 7:17 AM, Alexandre Belloni <
alexandre.belloni@free-electrons.com> wrote:

> Hi,
>
> That's mostly good
>
> On 22/02/2018 at 12:04:32 -0800, David Daney wrote:
> > +     priv->rtc->ops = &isl12026_rtc_ops;
> > +     priv->rtc->nvram_old_abi = false;
>
> This allocation is not necessary and I would refer not having t so when
> the ABI goes away, it is not necessary to change this driver.
>
> > +     ret = rtc_register_device(priv->rtc);
> > +     if (ret)
> > +             return ret;
> > +
> > +     memset(&nvm_cfg, 0, sizeof(nvm_cfg));
> > +     nvm_cfg.name = "eeprom";
>
> You probably need something more descriptive, usually the rtc model name
> else, it is difficult (but not impossible) to find where this nvmem is
> actually located when using /sys/bus/nvmem/devices
> isl12026- would be a good choice.
>
> > +     nvm_cfg.read_only = false;
> > +     nvm_cfg.root_only = true;
>
> any reason to have it root only?
>
> > +     nvm_cfg.base_dev = &client->dev;
> > +     nvm_cfg.priv = priv;
> > +     nvm_cfg.stride = 1;
> > +     nvm_cfg.word_size = 1;
> > +     nvm_cfg.size = 512;
> > +     nvm_cfg.reg_read = isl12026_nvm_read;
> > +     nvm_cfg.reg_write = isl12026_nvm_write;
> > +
> > +     return rtc_nvmem_register(priv->rtc, &nvm_cfg);
>
> The probe function must not fail after rtc_register_device has been
> called so you must return 0 here.
>
> It is not currently possible to call rtc_nvmem_register before
> rtc_register_device unless we move the nvmem to the parent device:
>
> diff --git a/drivers/rtc/nvmem.c b/drivers/rtc/nvmem.c
> index 3a02357eb783..17ec4c8d0fad 100644
> --- a/drivers/rtc/nvmem.c
> +++ b/drivers/rtc/nvmem.c
> @@ -91,7 +91,7 @@ int rtc_nvmem_register(struct rtc_device *rtc,
>         if (!nvmem_config)
>                 return -ENODEV;
>
> -       nvmem_config->dev = &rtc->dev;
> +       nvmem_config->dev = rtc->dev.parent;
>         nvmem_config->owner = rtc->owner;
>         rtc->nvmem = nvmem_register(nvmem_config);
>         if (IS_ERR_OR_NULL(rtc->nvmem))
>
> I'll submit this patch for this cycle before there are many users of the
> interface (converted drivers are still exposing the old ABI).
>
> If you prefer, you can depend on it.
>
> --
> Alexandre Belloni, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

[-- Attachment #2: Type: text/html, Size: 4067 bytes --]

  reply	other threads:[~2018-03-02 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 20:04 [PATCH v6] rtc: isl12026: Add driver David Daney
2018-02-28 15:17 ` Alexandre Belloni
2018-03-02 16:22   ` David Daney [this message]
2018-03-02 23:43     ` 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=CAKjEs9FbNDKNs5j-aZAmHCYO1YE5g70vLyuk1hGDNvvRWj977w@mail.gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=david.daney@cavium.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).