From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-hwmon@vger.kernel.org, jdelvare@suse.com, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, joel@jms.id.au
Subject: Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors
Date: Thu, 7 Sep 2017 17:27:25 -0700 [thread overview]
Message-ID: <cbbca5f6-4c40-d20e-b27d-2e965822ccb4@roeck-us.net> (raw)
In-Reply-To: <1504797770.5105.7.camel@aj.id.au>
On 09/07/2017 08:22 AM, Andrew Jeffery wrote:
> On Thu, 2017-09-07 at 06:40 -0700, Guenter Roeck wrote:
>> On 09/06/2017 04:32 PM, Andrew Jeffery wrote:
>>
>>>>
>>>> Guess I need to dig up my eval board and see if I can reproduce the problem.
>>>> Seems you are saying that the problem is always seen when issuing a sequence
>>>> of "clear faults" commands on multiple pages ?
>>>
>>> Yeah. We're also seeing bad behaviour under other command sequences as well,
>>> which lead to this hack of a work-around patch[1].
>>>
>>> I'd be very interested in the results of testing against the eval board. I
>>> don't have access to one and it seems Maxim have discontinued them.
>>>
>>
>> Do you have a somewhat reliable means to reproduce the problem ?
>
> It seems we hit a bunch of problems by just continually
> binding/unbinding the driver, if you don't apply that hacky oneshot
> retry patch. We can hit problems (in our design?) with something like:
>
> # cd /sys/bus/i2c/drivers/max31785; \
> echo $addr > unbind; \
> while echo $addr > bind; \
> do echo $addr > unbind; echo -n .; done;
>
> It should hit issues covered by this patch, as the register checks are
> used in the operations used by probe.
>
Hmm ... I didn't use your driver but my prototype driver which also supports
temperature and voltage attributes, so if anything it should create more
stress on the chip. No error so far, after running the script for a couple
of minutes. How long does it take for errors to appear, and how do I see
that there is an error ? Does the driver fail to instantiate ?
Guenter
next prev parent reply other threads:[~2017-09-08 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 7:01 Andrew Jeffery
2017-09-05 17:00 ` Guenter Roeck
2017-09-06 0:23 ` Andrew Jeffery
2017-09-06 22:51 ` Guenter Roeck
2017-09-06 23:32 ` Andrew Jeffery
2017-09-07 2:19 ` Guenter Roeck
2017-09-07 13:40 ` Guenter Roeck
2017-09-07 15:22 ` Andrew Jeffery
2017-09-08 0:27 ` Guenter Roeck [this message]
2017-09-08 1:02 ` Andrew Jeffery
2017-09-08 1:26 ` Guenter Roeck
2017-09-08 2:06 ` Andrew Jeffery
2017-09-08 2:17 ` Guenter Roeck
2017-09-08 2:51 ` Andrew Jeffery
2017-09-08 3:40 ` Andrew Jeffery
2017-09-08 4:43 ` Guenter Roeck
2017-09-08 5:08 ` Andrew Jeffery
2017-09-08 5:14 ` Guenter Roeck
2017-09-08 5:16 ` Andrew Jeffery
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=cbbca5f6-4c40-d20e-b27d-2e965822ccb4@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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
all inboxes | Powered by JetHome®