summaryrefslogtreecommitdiff
path: root/mausezahn.zsh
AgeCommit message (Expand)AuthorFilesLines
2014-07-25mausezahn: bind to IP address in interactive modeJon Schipp1-0/+1
2014-03-23zsh: Unify completion help messages for --version and --helpTobias Klauser1-2/+2
2013-06-04zsh: add zsh completion function for mausezahnHideo Hattori1-0/+67
ux/net-next.git/commit/?h=nds-private-remove&id=48cd30b49527f04078ef7de217cc188157f76ba6'>48cd30b49527f04078ef7de217cc188157f76ba6 (patch) tree062d3553ca1d5467bdf92717a5c23c8848c070a9 parentef37427ac5677331145ab27a17e6f5f1b43f0c11 (diff)
ARM: davinci: Make __clk_{enable,disable} functions public
In some cases, there is a need to enable a clock as part of clock enable callback of a different clock. For example, USB 2.0 PHY clock enable requires USB 2.0 clock to be enabled. In this case, it is safe to instead call __clk_enable() since the clock framework lock is already taken. Calling clk_enable() causes recursive locking error. A similar case arises in the clock disable path. To enable such usage, make __clk_{enable,disable} functions publicly available outside of clock.c. Also, call them davinci_clk_{enable|disable} now to be consistent with how other davinci-specific clock functions are named. Note that these functions are not exported to drivers. They are meant for usage in platform specific clock management code. Signed-off-by: Alexandre Bailon <abailon@baylibre.com> Suggested-by: David Lechner <david@lechnology.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Diffstat