From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Pratyush Yadav <p.yadav@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vadym Kochan <vadym.kochan@plvision.eu>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] eeprom: eeprom_93xx46: Add support for microchip 93LC46B eeprom
Date: Tue, 5 Jan 2021 16:28:10 +0530 [thread overview]
Message-ID: <20210105105817.17644-1-a-govindraju@ti.com> (raw)
This series of patches adds support for microchip 93LC46B eeprom by
- Adding a new compatible string
- Adding a quirk to send extra bit after the address to ignore the
zero bit sent before data, during a read transfer.
changes since v1:
- changed the compatible string to lower case.
- changed the variable for private data to lower case.
Aswath Govindraju (2):
Documentation: devicetree: Add new compatible string for eeprom
microchip 93LC46B
misc: eeprom_93xx46: Add quirk to support Microchip 93LC46B eeprom
.../devicetree/bindings/misc/eeprom-93xx46.txt | 1 +
drivers/misc/eeprom/eeprom_93xx46.c | 15 +++++++++++++++
include/linux/eeprom_93xx46.h | 2 ++
3 files changed, 18 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-05 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:58 Aswath Govindraju [this message]
2021-01-05 10:58 ` [PATCH v2 1/2] Documentation: devicetree: Add new compatible string for eeprom microchip 93LC46B Aswath Govindraju
2021-01-11 23:32 ` Rob Herring
2021-01-05 10:58 ` [PATCH v2 2/2] misc: eeprom_93xx46: Add quirk to support Microchip 93LC46B eeprom Aswath Govindraju
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=20210105105817.17644-1-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=p.yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=vadym.kochan@plvision.eu \
--cc=vigneshr@ti.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 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).