From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Brandt <Chris.Brandt@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] ARM: dts: r7s72100: fix sdhi clock define
Date: Mon, 16 Jan 2017 12:40:23 +0100 [thread overview]
Message-ID: <20170116114023.GA3029@katana> (raw)
In-Reply-To: <CAMuHMdX=cNuBSMqvPKYa7J5g7T4dSfHhSjcGdmuOPw_as=6RQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
> > and then in the code do:
> >
> > struct *cd_clk;
> > cd_clk = devm_clk_get(&pdev->dev, "cd");
> > if (cd_clk) {
> > clk_prepare_enable(cd_clk);
> > }
> >
> > (this simple 1-line fix patch is getting a lot more complicated)
>
> Disclaimer: I don't know how/if the SDHI core manages clocks, and may
> interfere. Adding Wolfram.
Thanks for the heads up.
We have special callbacks for en-/disabling clocks:
sh_mobile_sdhi_clk_enable() and sh_mobile_sdhi_clk_disable().
I think those functions should get the above if-blocks (without curly
braces) to ensure we always have consistent 00 or 11 settings.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-16 11:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:11 [PATCH] ARM: dts: r7s72100: fix sdhi clock define Chris Brandt
2017-01-12 18:11 ` Chris Brandt
2017-01-12 19:57 ` Geert Uytterhoeven
2017-01-12 20:34 ` Chris Brandt
2017-01-12 20:34 ` Chris Brandt
2017-01-13 8:35 ` Simon Horman
2017-01-13 14:44 ` Chris Brandt
2017-01-13 14:44 ` Chris Brandt
2017-01-13 15:10 ` Geert Uytterhoeven
2017-01-13 15:10 ` Geert Uytterhoeven
2017-01-13 17:16 ` Chris Brandt
2017-01-13 17:16 ` Chris Brandt
2017-01-13 17:31 ` Geert Uytterhoeven
2017-01-13 17:56 ` Chris Brandt
2017-01-13 17:56 ` Chris Brandt
2017-01-16 10:36 ` Geert Uytterhoeven
2017-01-16 10:36 ` Geert Uytterhoeven
2017-01-16 11:40 ` Wolfram Sang [this message]
2017-01-17 4:27 ` Chris Brandt
2017-01-17 4:27 ` Chris Brandt
2017-01-17 8:21 ` Wolfram Sang
2017-01-17 8:21 ` Wolfram Sang
2017-01-17 9:16 ` Geert Uytterhoeven
2017-01-17 9:16 ` Geert Uytterhoeven
2017-01-17 9:45 ` Wolfram Sang
2017-01-17 9:52 ` Geert Uytterhoeven
2017-01-17 9:57 ` Wolfram Sang
2017-01-17 9:57 ` Wolfram Sang
2017-01-17 10:00 ` Geert Uytterhoeven
2017-01-17 10:00 ` Geert Uytterhoeven
2017-01-17 14:48 ` Chris Brandt
2017-01-17 18:42 ` Chris Brandt
2017-01-17 19:23 ` Wolfram Sang
2017-01-17 19:23 ` Wolfram Sang
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=20170116114023.GA3029@katana \
--to=wsa@the-dreams.de \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.