Received: by 10.223.164.202 with SMTP id h10csp9794wrb; Tue, 14 Nov 2017 10:13:45 -0800 (PST) X-Google-Smtp-Source: AGs4zMYYqX+vLAxkUSEDPQSw/fjKydOlgZmzaEOSE4oH24ssgQpiAn52MD8yD3R7/j0jluYMF0iw X-Received: by 10.99.8.194 with SMTP id 185mr12958390pgi.202.1510683225824; Tue, 14 Nov 2017 10:13:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510683225; cv=none; d=google.com; s=arc-20160816; b=bte0T2GNBguGIE/RknFadC0y49XGhj10BOrib32L4IeZQaJAnVKVJie8s3rLi3xrVd w+8oj35+ax7l7UYgWlZmH2Nex1K2CYphZKNJJbgdYcFTvEGDm/d96UcnQewx+RuTdBBJ wCyTfB6o9W+yij3gATml1b69IcbUqgIMEKT2SROJuGAIe0jDUmLYv8XBiRrUkDm/1J8G nIsvkeOrcLVvg2+uu2y9TlwA9Z7trLSk5Sgo1XoVmF94g73UrIjsgNPXuR0T2WWog9jt poKknS1+rOnWRfmT+ZvJucF/Q0Qecjn6/J7bP9mR0LcskuC1I7nM4JKE3JVhhCZ05ctJ VvpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=P/fQnKiyU5Mo+W+pD3C70We0hC6fJtFnBN+3c0jZUFU=; b=PR+IbLmX8rDwOENqdVzXE60m88XnAawmVlEiVMi9DxIJkTDEO1BdeABBKmh/LJdpMp HfnaB7sAxqlm0XMKckowvhrTSCJLpVmqD3T/2zrD3D0EtpbDn+6XVDMWGrl51m0CIP0f wqTfTgEptym4Lkbld6TZLInf0VrntpOlf3lD/nTU0nMOT1BPF6XUXxS/BVOQuYpRoPpb XOL5fTKfoddBLtImD75IuZovau9w4MikRgKpDL0o+fLMvxyTMN5pgibFeKr+KbCmJq9r l3yh4eGh97RFkuA1HEkeSxNLnDsw7YYj5whAmw6iwH6Gsl0ISSFPKagBe90ylRVDgtlq t75g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=EzRTPMc0; dkim=pass header.i=@codeaurora.org header.s=default header.b=EzRTPMc0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j11si13940310plt.359.2017.11.14.10.13.33; Tue, 14 Nov 2017 10:13:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=EzRTPMc0; dkim=pass header.i=@codeaurora.org header.s=default header.b=EzRTPMc0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755172AbdKNSMW (ORCPT + 88 others); Tue, 14 Nov 2017 13:12:22 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:36752 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753931AbdKNSMO (ORCPT ); Tue, 14 Nov 2017 13:12:14 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id E706B600C9; Tue, 14 Nov 2017 18:12:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1510683133; bh=Mnun40bWmh8bvQOFxvOqihErC9afUHOGJGvjA+K81i0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EzRTPMc0SmfSqTR+d6pHczkZmBl8hqi4J7GXBM5U8eVe+floOf9HXBSRJ0Wo5f79Z HOir/8KEyMlqoy5HQHFTJdDVpkcB+TDfF8K8jxv3DDBPwp6rNa9dU+gn65FOX8uEGe /5O2yUT+bnSUzPK3d7qkdyRx+o/K5O399dOdWwIA= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from localhost (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sboyd@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 3721A600C9; Tue, 14 Nov 2017 18:12:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1510683133; bh=Mnun40bWmh8bvQOFxvOqihErC9afUHOGJGvjA+K81i0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EzRTPMc0SmfSqTR+d6pHczkZmBl8hqi4J7GXBM5U8eVe+floOf9HXBSRJ0Wo5f79Z HOir/8KEyMlqoy5HQHFTJdDVpkcB+TDfF8K8jxv3DDBPwp6rNa9dU+gn65FOX8uEGe /5O2yUT+bnSUzPK3d7qkdyRx+o/K5O399dOdWwIA= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 3721A600C9 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sboyd@codeaurora.org Date: Tue, 14 Nov 2017 10:12:12 -0800 From: Stephen Boyd To: Bjorn Andersson Cc: Georgi Djakov , jassisinghbrar@gmail.com, robh+dt@kernel.org, mturquette@baylibre.com, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v9 3/7] mailbox: qcom: Move the apcs struct into a separate header Message-ID: <20171114181212.GC11955@codeaurora.org> References: <20170921164940.20343-1-georgi.djakov@linaro.org> <20170921164940.20343-4-georgi.djakov@linaro.org> <20171026042811.GL1575@tuxbook> <5bad4c4b-362b-ba9f-3072-1cced7a004dd@linaro.org> <20171114021255.GY11955@codeaurora.org> <20171114044702.GF28761@minitux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171114044702.GF28761@minitux> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/13, Bjorn Andersson wrote: > On Mon 13 Nov 18:12 PST 2017, Stephen Boyd wrote: > > > On 10/27, Georgi Djakov wrote: > > > Hi Bjorn, > > > > > > Thanks for reviewing! > > > > > > On 10/26/2017 07:28 AM, Bjorn Andersson wrote: > > > > On Thu 21 Sep 09:49 PDT 2017, Georgi Djakov wrote: > > > > > > > >> Move the structure shared by the APCS IPC device and its subdevices > > > >> into a separate header file. > > > >> > > > > > > > > As you're creating the apcs regmap with devm_regmap_init_mmio() you can > > > > just call dev_get_regmap(dev->parent) in your child to get the handle. > > > > > > Ok, thanks! > > > > > > > > > > > But I would prefer that you just add the clock code to the existing > > > > driver. > > > > > > This will require an ack from Stephen, and i got the impression that he > > > prefers a separate clk driver [1]. > > > > > > Stephen, are you ok with registering the clocks from the apcs mailbox > > > driver? > > > > > > [1] https://lkml.org/lkml/2017/6/26/750 > > > > The parent regmap "trick" was the plan. Is something wrong with > > that? > > > > Not at all, but then this patch (moving apcs context to a shared header > file) shouldn't be needed, or am I missing something? Agreed. > > > Not having random clk drivers scattered throughout the tree is > > sort of nice because it makes for an easier time finding things > > that are similar. Maybe that's an abuse of the driver model > > though? Just to get things into some same directory. I'm fine > > either way. > > > > Keeping the clock driver in the clock subsystem does make sense. I see > now that there is a include of a local header file as well, so that > would just be messy to keep split. > > I'm fine with the extra driver instance, it's the DT that I don't think > should describe the fact that we want to keep the clock-part in the > clock subsystem. > > Do you see any problems spawning the clock driver programmatically and > then calling of_clk_add_hw_provider() on the parent's of_node? Nope. We shouldn't need to modify DT to make this work. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project From 1584015493222214831@xxx Tue Nov 14 04:48:12 +0000 2017 X-GM-THRID: 1579168714736773466 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread