From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Bibby Hsieh <bibby.hsieh@mediatek.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
Tomasz Figa <tfiga@chromium.org>,
Nicolas Boichat <drinkcat@chromium.org>,
srv_heupstream <srv_heupstream@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH v10 3/4] misc: eeprom: at24: support pm_runtime control
Date: Thu, 23 Jan 2020 12:56:29 +0100 [thread overview]
Message-ID: <CAMpxmJX=qh3oSgOtB6ciKG2tJW5VvYXEqw7ZWPM21_ynaXe++w@mail.gmail.com> (raw)
In-Reply-To: <20200116025637.3524-4-bibby.hsieh@mediatek.com>
czw., 16 sty 2020 o 03:56 Bibby Hsieh <bibby.hsieh@mediatek.com> napisał(a):
>
> Although in the most platforms, the power of eeprom are alway
> on, some platforms disable the eeprom power in order to meet
> low power request. This patch add the pm_runtime ops to control
> power to support all platforms.
>
> Signed-off-by: Bibby Hsieh <bibby.hsieh@mediatek.com>
Patch applied.
Bartosz
next prev parent reply other threads:[~2020-01-23 11:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 2:56 [PATCH v10 0/4] add power control in i2c and at24 Bibby Hsieh
2020-01-16 2:56 ` [PATCH v10 1/4] dt-binding: eeprom: at24: add vcc-supply property Bibby Hsieh
2020-01-23 11:56 ` Bartosz Golaszewski
2020-01-16 2:56 ` [PATCH v10 2/4] dt-binding: i2c: add bus-supply property Bibby Hsieh
2020-01-16 2:56 ` [PATCH v10 3/4] misc: eeprom: at24: support pm_runtime control Bibby Hsieh
2020-01-23 11:56 ` Bartosz Golaszewski [this message]
2020-01-16 2:56 ` [PATCH v10 4/4] i2c: core: support bus regulator controlling in adapter Bibby Hsieh
2020-01-28 3:57 ` Tomasz Figa
2020-01-28 6:36 ` Wolfram Sang
2020-01-28 7:32 ` Tomasz Figa
2020-01-28 7:31 ` Tomasz Figa
2020-02-17 9:45 ` Tomasz Figa
2020-02-21 3:22 ` Bibby Hsieh
2020-02-24 22:28 ` Rafael J. Wysocki
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='CAMpxmJX=qh3oSgOtB6ciKG2tJW5VvYXEqw7ZWPM21_ynaXe++w@mail.gmail.com' \
--to=bgolaszewski@baylibre.com \
--cc=bibby.hsieh@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).