From: Andrew Lunn <andrew@lunn.ch>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: GregKH <greg@kroah.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Wolfram Sang <wsa@the-dreams.de>,
broonie@kernel.org, vz@mleia.com, fd@ti.com,
LKML <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH 3/7] eeprom: at24: extend driver to plug into the NVMEM framework
Date: Tue, 2 Feb 2016 03:28:50 +0100 [thread overview]
Message-ID: <20160202022850.GF12673@lunn.ch> (raw)
In-Reply-To: <CAMpxmJX1nFMmKroxMLWPyTAzkKB50bZnE4Pu=0ch1CfR7FhNXw@mail.gmail.com>
> Hi Andrew,
>
> the patch works, but I'm hitting the following BUG when instantiating
> an at24c32 device:
>
> # echo 24c32 0x54 > /sys/class/i2c-adapter/i2c-2/new_device
Ah, i did'n't tests it this way. I have my devices in device tree.
Thanks for the report. I will reproduce this in the next few days and
see about fixing it.
Andrew
next prev parent reply other threads:[~2016-02-02 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 15:42 [PATCH 0/7] Convert exiting EEPROM drivers to NVMEM Andrew Lunn
2016-01-28 15:42 ` [PATCH 1/7] nvmem: Add flag to export NVMEM to root only Andrew Lunn
2016-01-28 15:42 ` [PATCH 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers Andrew Lunn
2016-01-28 15:42 ` [PATCH 3/7] eeprom: at24: extend driver to plug into the NVMEM framework Andrew Lunn
2016-01-29 13:10 ` Bartosz Golaszewski
2016-02-02 2:28 ` Andrew Lunn [this message]
2016-02-12 9:16 ` Andrew Lunn
2016-02-12 11:02 ` Bartosz Golaszewski
2016-01-28 15:42 ` [PATCH 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM Andrew Lunn
2016-01-28 15:42 ` [PATCH 5/7] eeprom: at25: extend driver to plug into the NVMEM framework Andrew Lunn
2016-01-28 15:42 ` [PATCH 6/7] eeprom: 93xx46: " Andrew Lunn
2016-01-28 15:42 ` [PATCH 7/7] misc: at24: replace memory_accessor with nvmem_device_read Andrew Lunn
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=20160202022850.GF12673@lunn.ch \
--to=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=fd@ti.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vz@mleia.com \
--cc=wsa@the-dreams.de \
/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
Powered by JetHome