From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: socfpga: dts: Add a clock node for sdmmc CIU
Date: Wed, 13 May 2015 11:09:36 -0700 [thread overview]
Message-ID: <20150513180936.GG15988@codeaurora.org> (raw)
In-Reply-To: <5553671E.3070301@opensource.altera.com>
On 05/13, Dinh Nguyen wrote:
>
>
> On 5/13/15 2:54 AM, Stephen Boyd wrote:
> > On 04/14, dinguyen at opensource.altera.com wrote:
> >> From: Dinh Nguyen <dinguyen@opensource.altera.com>
> >>
> >> The CIU(Card Interface Unit) get its clock from the sdmmc_clk_divided clock
> >> which is used to clock the card. The sdmmc_clk_divided clock is the sdmmc_clk
> >> passed through a fixed divider of 4. This patch adds the sdmmc_clk_divided
> >> node and makes the sdmmc_clk it's parent.
> >>
> >> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> >> ---
> >
> > Is this a fix of some sort? I'm confused why this was sent to the
> > clk maintainers when it seems to be more appropriate to go
> > through the arm-soc tree.
> >
>
> Ok, sorry about that. I thought since it was clock nodes, it would
> appropriate to CC clk maintainers.
Sure, Cc is fine, but I believe the mail was sent "To" us so that
led to my confusion.
>
> BTW, can I take patches from drivers/clk/socfpga/* through the arm-soc
> tree or would that go through you guys?
>
Unless there's some sort of complicated dependency between the
clk tree and the arm-soc tree I'd prefer any patches against
drivers/clk/* go through the clk tree.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-05-13 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 16:05 [PATCHv2] ARM: socfpga: dts: Add a clock node for sdmmc CIU dinguyen at opensource.altera.com
2015-05-13 7:54 ` Stephen Boyd
2015-05-13 15:00 ` Dinh Nguyen
2015-05-13 18:09 ` Stephen Boyd [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=20150513180936.GG15988@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).