[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jul 2015 10:54:55 +0530
From: Jassi Brar <jassisinghbrar@...il.com>
To: Leo Yan <leo.yan@...aro.org>
Cc: Russell King <linux@....linux.org.uk>,
Michael Turquette <mturquette@...libre.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Query: Clock driver requests mailbox channel
On Mon, Jul 6, 2015 at 5:03 PM, Leo Yan <leo.yan@...aro.org> wrote:
> Hi all,
>
> i'm working with one clock driver, which will invoke mailbox API to
> request the mailbox channel and send message.
>
> Usually clock driver will init with devicetree, below is the example:
> CLK_OF_DECLARE(hi6220_clk_power, "hisilicon,hi6220-clock-power",
> hi6220_clk_power_init);
>
> Clock init function it will pass the pointer of struct device_node
> but not the pointer of struct device. So finally it's difficult to
> invoke mailbox API *mbox_request_channel()*, due it need use the
> struct device to search DT's property "mboxes".
>
> I want to find which is the best way to resolve this issue, so do you
> suggest clock driver to manually register one device? Or can we add
> one more API to request the mailbox channel directly with device_node?
>
IIUC, such clocks (that require platform resources) should be
populated from the platform_device's probe()?
--
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