From: peda@lysator.liu.se (Peter Rosin)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression: at24 eeprom writing
Date: Sun, 4 Oct 2015 21:50:28 +0200 [thread overview]
Message-ID: <56118304.8020002@lysator.liu.se> (raw)
In-Reply-To: <560F0DB1.2020101@lysator.liu.se>
On 2015-10-03 01:05, Peter Rosin wrote:
> I looked around and found that if I revert a839ce663b3183209fdf7b1fc4796bfe2a4679c3
> "eeprom: at24: extend driver to allow writing via i2c_smbus_write_byte_data"
> eeprom writing starts working again.
>
> AFAICT, the i2c-at91 bus driver makes the eeprom driver use the
> i2c_transfer code path both with that patch and with it reverted,
> so I sadly don't see why the patch makes a difference.
And now when I retry the same thing, that patch is no longer affecting things.
I must have confused myself over what kernel was actually running. Christian,
please accept my deepest apologies for implicating you in this regression.
But the regression is still there. In short, linux-3.18-at91 from the
linux4sam tree works, linux-4.1-at91 from the same tree does not, and
vanilla 4.2 also doesn't work. I have a hard time bisecting this thing
though, since the last known good version has a long list of atmel
patches that I refuse to even try to rebase...
Ideas still welcome of course.
Cheers,
Peter
next prev parent reply other threads:[~2015-10-04 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 23:05 Regression: at24 eeprom writing Peter Rosin
2015-10-04 19:50 ` Peter Rosin [this message]
2015-10-05 6:16 ` Christian Gmeiner
2015-10-06 16:41 ` Peter Rosin
2015-10-05 8:45 ` Peter Rosin
2015-10-05 8:59 ` kbuild test robot
2015-10-05 15:00 ` Ludovic Desroches
2015-10-05 15:09 ` Peter Rosin
2015-10-12 15:13 ` Peter Rosin
2015-10-12 16:13 ` Cyrille Pitchen
2015-10-13 10:38 ` Peter Rosin
2015-10-13 12:57 ` Nicolas Ferre
2015-10-13 14:35 ` Peter Rosin
2015-10-13 13:26 ` ludovic.desroches at atmel.com
2015-10-05 15:28 ` Cyrille Pitchen
2015-10-05 15:54 ` Peter Rosin
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=56118304.8020002@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=linux-arm-kernel@lists.infradead.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).