From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vadym Kochan <vadym.kochan@plvision.eu>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>
Subject: [PATCH RFC 0/2] eeprom: eeprom_93xx46: Add support for sending zero bits after address during read transfer
Date: Wed, 9 Dec 2020 23:27:06 +0530 [thread overview]
Message-ID: <20201209175708.16252-1-a-govindraju@ti.com> (raw)
The following series of patches adds support for sending zero bits after
address during read transfer, through a device tree property.
Aswath Govindraju (2):
Documentation: devicetree: Add property for ignoring the dummy bits
sent before read transfer
eeprom: eeprom_93xx46: Add support for ignoring the dummy bit
preceding data during read transfer
.../bindings/misc/eeprom-93xx46.txt | 4 +++-
drivers/misc/eeprom/eeprom_93xx46.c | 23 +++++++++++++++++++
include/linux/eeprom_93xx46.h | 6 +++++
3 files changed, 32 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2020-12-09 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 17:57 Aswath Govindraju [this message]
2020-12-09 17:57 ` [PATCH RFC 1/2] Documentation: devicetree: Add property for ignoring the dummy bits sent before read transfer Aswath Govindraju
2020-12-11 3:33 ` Rob Herring
2020-12-11 15:04 ` Aswath Govindraju
2020-12-14 22:23 ` Rob Herring
2020-12-15 16:12 ` Aswath Govindraju
2020-12-17 13:48 ` Aswath Govindraju
2020-12-17 15:48 ` Rob Herring
2020-12-17 16:02 ` Aswath Govindraju
2020-12-09 17:57 ` [PATCH RFC 2/2] eeprom: eeprom_93xx46: Add support for ignoring the dummy bit preceding data during " 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=20201209175708.16252-1-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@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).