Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754621AbbGFLeG (ORCPT ); Mon, 6 Jul 2015 07:34:06 -0400 Received: from mail-pa0-f52.google.com ([209.85.220.52]:35050 "EHLO mail-pa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754069AbbGFLeC (ORCPT ); Mon, 6 Jul 2015 07:34:02 -0400 Date: Mon, 6 Jul 2015 19:33:55 +0800 From: Leo Yan To: Russell King , Michael Turquette , Jassi Brar , linux-kernel@vger.kernel.org Subject: Query: Clock driver requests mailbox channel Message-ID: <20150706113355.GA6967@leoy-linaro> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1028 Lines: 27 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? Welcome any suggestion. Thanks, Leo Yan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/