From: Heiko Schocher <hs@denx.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-kernel@vger.kernel.org, Georg.Soffel@bosch-si.com,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] rtc: pcf8563: add CLKOUT to common clock framework
Date: Fri, 16 Oct 2015 13:31:57 +0200 [thread overview]
Message-ID: <5620E02D.2000605@denx.de> (raw)
In-Reply-To: <20151016110051.GM3421@piout.net>
Hello Alexandre,
Am 16.10.2015 um 13:00 schrieb Alexandre Belloni:
> On 16/10/2015 at 12:54:46 +0200, Alexandre Belloni wrote :
>>> +static struct clk *pcf8563_clkout_register_clk(struct pcf8563 *pcf8563)
>>> +{
>>> + struct i2c_client *client = pcf8563->client;
>>> + struct device_node *node = client->dev.of_node;
>>> + struct clk *clk;
>>> + struct clk_init_data init;
>>> + int ret;
>>> + unsigned char buf;
>>> +
>>> + /* disable the clkout output */
>>> + buf = 0;
>>> + ret = pcf8563_write_block_data(client, PCF8563_REG_CLKO, 1, &buf);
>>> + if (ret < 0)
>>> + return ERR_PTR(ret);
>>> +
>>
>> Isn't that done automatically for an unused clock? However, I would do
>> that in the probe as you will have to sprinkle some #ifdef
>> CONFIG_COMMON_CLK after seeing the kbuild report.
>
> I'm rethinking about your comment about breaking existing boards. I'd
> say that probably nobody is using the output from the rtc but maybe
> (highly unlikely) some are configuring it from the bootloader and in
> that case it is not nice to undo that configuration. Let's keep that
> block here as long as it works fine for you.
Ok, so I have also a better feeling with it ... removing it back ;-)
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2015-10-16 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 7:59 [PATCH v2] rtc: pcf8563: add CLKOUT to common clock framework Heiko Schocher
2015-10-16 10:22 ` kbuild test robot
2015-10-16 10:46 ` kbuild test robot
2015-10-16 10:54 ` Alexandre Belloni
[not found] ` <20151016105446.GK3421-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2015-10-16 11:00 ` Alexandre Belloni
2015-10-16 11:31 ` Heiko Schocher [this message]
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=5620E02D.2000605@denx.de \
--to=hs@denx.de \
--cc=Georg.Soffel@bosch-si.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).