From: York Sun <yorksun-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Michael Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Common clock framework examples
Date: Thu, 28 May 2015 15:52:28 -0700 [thread overview]
Message-ID: <55679C2C.2080100@freescale.com> (raw)
Michael,
Let me start a new thread for more questions regarding common clock framework.
Following yours and other experts' suggestion, I start to write a new driver for
SI5338. As I explained earlier, I have multiple clock chips. They may have
different clock sources. I haven't figured out how to put them into device tree
because the clocks chips are on PCIe cards.
Let's say I want to initialize without device tree. Is there an example to setup
platform data structure so I can put in the clock rate of xtal or clk_in?
York
WARNING: multiple messages have this Message-ID (diff)
From: York Sun <yorksun@freescale.com>
To: Michael Turquette <mturquette@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sebastian.hesselbarth@gmail.com>
Subject: Common clock framework examples
Date: Thu, 28 May 2015 15:52:28 -0700 [thread overview]
Message-ID: <55679C2C.2080100@freescale.com> (raw)
Michael,
Let me start a new thread for more questions regarding common clock framework.
Following yours and other experts' suggestion, I start to write a new driver for
SI5338. As I explained earlier, I have multiple clock chips. They may have
different clock sources. I haven't figured out how to put them into device tree
because the clocks chips are on PCIe cards.
Let's say I want to initialize without device tree. Is there an example to setup
platform data structure so I can put in the clock rate of xtal or clk_in?
York
next reply other threads:[~2015-05-28 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 22:52 York Sun [this message]
2015-05-28 22:52 ` Common clock framework examples York Sun
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=55679C2C.2080100@freescale.com \
--to=yorksun-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.