lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <55679C2C.2080100@freescale.com>
Date:	Thu, 28 May 2015 15:52:28 -0700
From:	York Sun <yorksun@...escale.com>
To:	Michael Turquette <mturquette@...aro.org>
CC:	Guenter Roeck <linux@...ck-us.net>, <linux-i2c@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <sebastian.hesselbarth@...il.com>
Subject: Common clock framework examples

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ