From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Rob Herring <robh@kernel.org>
Cc: Jeppe Ledet-Pedersen <jlp@gomspace.com>,
lee.jones@linaro.org, arnd@arndb.de, gregkh@linuxfoundation.org,
a.zummo@towertech.it, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rtc-linux@googlegroups.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH 1/3] mfd: add Cypress FM33256B Processor Companion driver
Date: Fri, 22 Apr 2016 22:11:53 +0200 [thread overview]
Message-ID: <20160422201153.GB17051@piout.net> (raw)
In-Reply-To: <20160422193232.GA9737@rob-hp-laptop>
On 22/04/2016 at 14:32:32 -0500, Rob Herring wrote :
> On Wed, Apr 20, 2016 at 01:07:49PM +0200, Jeppe Ledet-Pedersen wrote:
> > This patch adds support for the Cypress Semiconductor FM33256B processor
> > companion. The device contains a 256 kbit FRAM, an RTC, a supply voltage
> > monitor, and a watchdog timer.
> >
> > Signed-off-by: Jeppe Ledet-Pedersen <jlp@gomspace.com>
> > ---
> > Documentation/devicetree/bindings/mfd/fm33256b.txt | 30 ++
> > MAINTAINERS | 6 +
> > drivers/mfd/Kconfig | 16 +
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/fm33256b.c | 488 +++++++++++++++++++++
> > include/linux/mfd/fm33256b.h | 76 ++++
> > 6 files changed, 617 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/mfd/fm33256b.txt
> > create mode 100644 drivers/mfd/fm33256b.c
> > create mode 100644 include/linux/mfd/fm33256b.h
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/fm33256b.txt b/Documentation/devicetree/bindings/mfd/fm33256b.txt
> > new file mode 100644
> > index 0000000..6591c94
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/fm33256b.txt
> > @@ -0,0 +1,30 @@
> > +Device-tree bindings for Cypress Semiconductor FM33256B Processor Companion
> > +---------------------------------------------------------------------------
> > +
> > +Required properties:
> > +- compatible: must be "cypress,fm33256b".
> > +- reg: SPI chip select
> > +- spi-max-frequency: Max SPI frequency to use (< 16000000)
> > +
> > +Optional properties:
> > +- cypress,charge-enabled: enable trickle charger
>
> What does the driver do if charging is disabled? Would using 'status =
> "disabled"' be any different?
>
Good catch, I didn't look at this patch but it includes a lot of code
that should be going to the RTC driver.
If trickle charging is not enabled, I guess the RTC will not charge its
backup battery.
> > +- cypress,charge-fast: enable fast (1 mA) charging
>
> What does fast mean?
>
> I think it is time for a common binding here. There's all sorts of
> variations on setting the charge current in bindings. Add something like
> "charge-current-microamp" in power_supply.txt and use it here. Then
> 1000uA implies "fast charge".
Well, this is not a power supply, it is an RTC.
I think both properties should got to the RTC subdevice and be parsed in
the RTC driver.
Note that for trickle charging, we currently have the following
properties:
- trickle-resistor-ohms
- trickle-diode-disable
- abracon,tc-diode
- abracon,tc-resistor
abracon,tc-resistor can be replaced by trickle-resistor-ohms, I'll make
a patch but abracon,tc-diode allows to select a diode type (and in
particular a voltage drop).
I think we could add a trickle-current-microamp like you suggested and
trickle-diode-disable can be reused.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-04-22 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 11:07 [rtc-linux] [PATCH 0/3] Cypress FM33256B processor companion support Jeppe Ledet-Pedersen
2016-04-20 11:07 ` [rtc-linux] [PATCH 1/3] mfd: add Cypress FM33256B Processor Companion driver Jeppe Ledet-Pedersen
2016-04-22 0:47 ` [rtc-linux] " kbuild test robot
2016-04-22 19:32 ` Rob Herring
2016-04-22 20:11 ` Alexandre Belloni [this message]
2016-04-26 14:31 ` Jeppe Ledet-Pedersen
2016-05-03 8:14 ` Alexandre Belloni
2016-04-26 14:42 ` Jeppe Ledet-Pedersen
2016-04-20 11:07 ` [rtc-linux] [PATCH 2/3] misc: eeprom: add Cypress FM33256B FRAM driver Jeppe Ledet-Pedersen
2016-04-21 23:54 ` [rtc-linux] " Alexandre Belloni
2016-04-26 12:08 ` Jeppe Ledet-Pedersen
2016-04-20 11:07 ` [rtc-linux] [PATCH 3/3] rtc: add Cypress FM33256B RTC driver Jeppe Ledet-Pedersen
2016-04-21 23:44 ` [rtc-linux] " Alexandre Belloni
2016-04-26 12:17 ` Jeppe Ledet-Pedersen
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=20160422201153.GB17051@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jlp@gomspace.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh@kernel.org \
--cc=rtc-linux@googlegroups.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