From: Eliav Farber <farbere@amazon.com>
To: <brgl@bgdev.pl>, <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<arnd@arndb.de>, <gregkh@linuxfoundation.org>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <farbere@amazon.com>, <talel@amazon.com>, <hhhawa@amazon.com>,
<jonnyc@amazon.com>, <hanochu@amazon.com>, <ronenk@amazon.com>,
<itamark@amazon.com>, <shellykz@amazon.com>, <shorer@amazon.com>,
<amitlavi@amazon.com>, <almogbs@amazon.com>, <dkl@amazon.com>,
<dwmw@amazon.co.uk>
Subject: [PATCH v3 0/2] add power-supply control to enable eeprom usage
Date: Sun, 28 Aug 2022 15:49:02 +0000 [thread overview]
Message-ID: <20220828154904.20477-1-farbere@amazon.com> (raw)
First patch describes the new binding property.
Second patch adds the functionality to the driver.
Change between v3 and v2:
- Apply on top of v6.0-rc1.
Change between v2 and v1:
- Use a gpio regulator for power-supply control.
Eliav Farber (2):
dt-bindings: at24: add new optional power-supply property
eeprom: at24: add support for power-supply control
.../devicetree/bindings/eeprom/at24.yaml | 4 ++
drivers/misc/eeprom/at24.c | 40 +++++++++++++++++++
2 files changed, 44 insertions(+)
--
2.37.1
next reply other threads:[~2022-08-28 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 15:49 Eliav Farber [this message]
2022-08-28 15:49 ` [PATCH v3 1/2] dt-bindings: at24: add new optional power-supply property Eliav Farber
2022-08-29 18:55 ` Rob Herring
2022-08-28 15:49 ` [PATCH v3 2/2] eeprom: at24: add support for power-supply control Eliav Farber
2022-08-31 13:00 ` [PATCH v3 0/2] add power-supply control to enable eeprom usage Bartosz Golaszewski
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=20220828154904.20477-1-farbere@amazon.com \
--to=farbere@amazon.com \
--cc=almogbs@amazon.com \
--cc=amitlavi@amazon.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=dkl@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=itamark@amazon.com \
--cc=jonnyc@amazon.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=shellykz@amazon.com \
--cc=shorer@amazon.com \
--cc=talel@amazon.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).