Lines Matching refs:of

6 detailed explanation of the clock api in include/linux/clk.h, but
12 available on various devices today.  This may come in the form of clock
17 details of its counterpart.  First is the common definition of struct
19 has traditionally been duplicated across a variety of platforms.  Second
20 is a common implementation of the clk.h api, defined in
24 The second half of the interface is comprised of the hardware-specific
27 the remainder of this document any reference to a callback in struct
29 implementation of that code.  Likewise, references to struct clk_foo
30 serve as a convenient shorthand for the implementation of the
33 Tying the two halves of this interface together is struct clk_hw, which
35 allows for easy navigation between the two discrete halves of the common
55 The members above make up the core of the clk tree topology.  The clk
60 clk_ops pointer in struct clk to perform the hardware-specific parts of
94 The strength of the common struct clk comes from its .ops and .hw pointers
95 which abstract the details of struct clk from the hardware-specific bits, and
129 And the definition of clk_gate_set_bit:
144 This pattern of abstraction is used for every clock hardware
149 When implementing support for a new type of clock it only necessary to
166 To take advantage of your data you'll need to support valid operations
190 hardware capabilities of that clock.  A cell marked as "y" means
218 [1] either one of round_rate or determine_rate is required.
229 	Part 5 - Disabling clock gating of unused clocks
232 default disabling of unused clocks. For example, if drivers aren't enabling
257 of one group, regardless of whether those resources are shared by multiple
259 of the two groups needs to be protected by the drivers. An example of such a
264 framework functions from within its implementation of clock operations. This
265 can for instance cause a .set_rate operation of one clock being called from
266 within the .set_rate operation of another clock. This case must be considered
270 Note that locking must also be considered when code outside of the common
272 is considered out of scope of this document.