All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	H Hartley Sweeten <hsweeten@visionengravers.com>
Cc: <rtc-linux@googlegroups.com>, Alessandro Zummo <a.zummo@towertech.it>
Subject: [rtc-linux] Re: [PATCH 1/5] rtc: m48t86: verify that the RTC is actually present
Date: Tue, 21 Feb 2017 17:47:48 +0000	[thread overview]
Message-ID: <15a61c951a0.27a8.15018831546f68f527b5b4b4e7f8f3cd@digriz.org.uk> (raw)
In-Reply-To: <20170221163720.m6hp27t4z7q4pgwl@piout.net>

Thanks, not tested though, as I am lacking in time at the moment.  I 
probably am the only ts7800 user in the world using a mainline kernel 
too...so will only be punishing myself :-)

Acked-By: Alexander Clouter <alex+kernel@digriz.org.uk>


On 21 February 2017 4:37:35 p.m. Alexandre Belloni 
<alexandre.belloni@free-electrons.com> wrote:

> Hi,
>
> On 15/02/2017 at 09:35:23 -0700, H Hartley Sweeten wrote:
>> The RTC is an optional feature at purchase time on some Technologic
>> Systems boards. Verify that it actually exists by checking if the
>> last two bytes of the NVRAM can be changed.
>>
>> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>> Cc: Alessandro Zummo <a.zummo@towertech.it>
>> Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>> Cc: Alexander Clouter <alex@digriz.org.uk>
>> ---
>>  drivers/rtc/rtc-m48t86.c | 36 ++++++++++++++++++++++++++++++++++++
>>  1 file changed, 36 insertions(+)
>>
>
> I've applied that one. Alex, if you are fine with the mach-orion5x
> changes, I can take them for 4.11. Else, this will wait for 4.12.
>
>> diff --git a/drivers/rtc/rtc-m48t86.c b/drivers/rtc/rtc-m48t86.c
>> index 4dc4af4..41ac5d6 100644
>> --- a/drivers/rtc/rtc-m48t86.c
>> +++ b/drivers/rtc/rtc-m48t86.c
>> @@ -201,6 +201,37 @@ static ssize_t m48t86_nvram_write(struct file *filp, 
>> struct kobject *kobj,
>>  static BIN_ATTR(nvram, 0644, m48t86_nvram_read, m48t86_nvram_write,
>>  		M48T86_NVRAM_LEN);
>>
>> +/*
>> + * The RTC is an optional feature at purchase time on some Technologic Systems
>> + * boards. Verify that it actually exists by checking if the last two bytes
>> + * of the NVRAM can be changed.
>> + *
>> + * This is based on the method used in their rtc7800.c example.
>> + */
>> +static bool m48t86_verify_chip(struct platform_device *pdev)
>> +{
>> +	unsigned int offset0 = M48T86_NVRAM_LEN - 2;
>> +	unsigned int offset1 = M48T86_NVRAM_LEN - 1;
>> +	unsigned char tmp0, tmp1;
>> +
>> +	tmp0 = m48t86_readb(&pdev->dev, offset0);
>> +	tmp1 = m48t86_readb(&pdev->dev, offset1);
>> +
>> +	m48t86_writeb(&pdev->dev, 0x00, offset0);
>> +	m48t86_writeb(&pdev->dev, 0x55, offset1);
>> +	if (m48t86_readb(&pdev->dev, offset1) == 0x55) {
>> +		m48t86_writeb(&pdev->dev, 0xaa, offset1);
>> +		if (m48t86_readb(&pdev->dev, offset1) == 0xaa &&
>> +		    m48t86_readb(&pdev->dev, offset0) == 0x00) {
>> +			m48t86_writeb(&pdev->dev, tmp0, offset0);
>> +			m48t86_writeb(&pdev->dev, tmp1, offset1);
>> +
>> +			return true;
>> +		}
>> +	}
>> +	return false;
>> +}
>> +
>>  static int m48t86_rtc_probe(struct platform_device *pdev)
>>  {
>>  	struct m48t86_rtc_info *info;
>> @@ -231,6 +262,11 @@ static int m48t86_rtc_probe(struct platform_device *pdev)
>>
>>  	dev_set_drvdata(&pdev->dev, info);
>>
>> +	if (!m48t86_verify_chip(pdev)) {
>> +		dev_info(&pdev->dev, "RTC not present\n");
>> +		return -ENODEV;
>> +	}
>> +
>>  	info->rtc = devm_rtc_device_register(&pdev->dev, "m48t86",
>>  					     &m48t86_rtc_ops, THIS_MODULE);
>>  	if (IS_ERR(info->rtc))
>> --
>> 2.10.0
>>
>
> --
> Alexandre Belloni, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com


-- 
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.
--- 
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 email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2017-02-21 17:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 16:35 [rtc-linux] [PATCH 0/5] rtc: m48t86: remove need for platform_data H Hartley Sweeten
2017-02-15 16:35 ` [rtc-linux] [PATCH 1/5] rtc: m48t86: verify that the RTC is actually present H Hartley Sweeten
2017-02-21 16:37   ` [rtc-linux] " Alexandre Belloni
2017-02-21 17:04     ` [rtc-linux] " Hartley Sweeten
2017-02-21 17:21       ` [rtc-linux] " Alexandre Belloni
2017-02-21 17:47     ` Alexander Clouter [this message]
2017-02-21 20:24       ` Alexandre Belloni
2017-02-15 16:35 ` [rtc-linux] [PATCH 2/5] ARM: Orion5x: ts78xx: remove RTC detection H Hartley Sweeten
2017-02-15 16:35 ` [rtc-linux] [PATCH 3/5] ARM: Orion5x: ts78xx: allow rtc-m48t86 to manage it's own resources H Hartley Sweeten
2017-02-15 16:35 ` [rtc-linux] [PATCH 4/5] ARM: ep93xx: ts72xx: " H Hartley Sweeten
2017-02-15 16:35 ` [rtc-linux] [PATCH 5/5] rtc: m48t86: remove unused platform_data H Hartley Sweeten

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=15a61c951a0.27a8.15018831546f68f527b5b4b4e7f8f3cd@digriz.org.uk \
    --to=alex@digriz.org.uk \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=hsweeten@visionengravers.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.