From: Jeppe Ledet-Pedersen <jlp@gomspace.com>
To: Rob Herring <robh@kernel.org>
Cc: <lee.jones@linaro.org>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>,
<alexandre.belloni@free-electrons.com>, <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: Tue, 26 Apr 2016 16:42:40 +0200 [thread overview]
Message-ID: <571F7E60.9040106@gomspace.com> (raw)
In-Reply-To: <20160422193232.GA9737@rob-hp-laptop>
On 22/04/16 21:32, Rob Herring wrote:
> On Wed, Apr 20, 2016 at 01:07:49PM +0200, Jeppe Ledet-Pedersen wrote:
[snip]
>> +
>> +The MFD exposes two subdevices:
>> +- The FRAM: "cypress,fm33256b-fram"
>> +- The RTC: "cypress,fm33256b-rtc"
>> +
>> +Example:
>> +
>> +spi1: spi@f800800 {
>> + status = "okay";
>> + cs-gpios = <&pioC 25 0>;
>> +
>> + fm33256b@0 {
>> + compatible = "cypress,fm33256b";
>> + spi-max-frequency = <10000000>;
>> + cypress,charge-enabled;
>> + cypress,charge-fast;
>> + reg = <0>;
>> + };
>
> Where's the 2nd sub device?
Hi Rob,
Right now I just add the two sub-devices using mfd_add_devices in the
fm33256b_probe function in my MFD driver. Would it be better to check
for compatible child nodes before adding each sub-device, like it's done
in drivers/mfd/tc3589x.c?
Thanks,
-Jeppe
--
--
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-26 14:44 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
2016-04-26 14:31 ` Jeppe Ledet-Pedersen
2016-05-03 8:14 ` Alexandre Belloni
2016-04-26 14:42 ` Jeppe Ledet-Pedersen [this message]
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=571F7E60.9040106@gomspace.com \
--to=jlp@gomspace.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--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