Received: by 10.223.185.116 with SMTP id b49csp1927718wrg; Thu, 22 Feb 2018 05:33:40 -0800 (PST) X-Google-Smtp-Source: AH8x225JREF3IFsOYNVSyP2DGBj7yHyhtJ1KUal3sR18XFCC+sSAOFJFShgc67+byD3DO8lATq6W X-Received: by 2002:a17:902:ab8c:: with SMTP id f12-v6mr6188745plr.171.1519306420249; Thu, 22 Feb 2018 05:33:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519306420; cv=none; d=google.com; s=arc-20160816; b=qhnpiWp5E0wRgg5BMeZr7KLcsyx1J2EtUPyfyzrOYW/PtxxFPwOcwquzCPQg8nUdEu fa6F++DalU8Dh8fxnaiBOQJezLyqdXN4yGGpZgD14B6NJuROeKsS6FNPRXnme0je6el0 Dies3VHx5nibv8CNsln8fV+tGJGxi2BCrVTNsjt33O1v7MEjLs/Wlz249OIW9oqRrU0+ B7mLswW+YJOQWVB48jkRRC1bqNVO6XtA1HmEy2pk6td59QXWkBrc2+NF6nqEvBhNPRwV PsYfr++PSvTbiFPO/W3mSr++UVBQOPS/iaXkNeJXTS6ZOElgywb3GGDgDEPGJ4FdqDKx 06xQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=Mw4O3/e4XcDTzK0Qk72i7gDEW+5Y37PNcDtmq/p9au0=; b=snMhxDS4RoGlxaRmC6OTBera9wmwmwXbe+QBRyDwwAP8f4xbKbgjntYAC2Z7E8+xSi wnrpmoAaTrHgSmyChP4fduIuFmV8Xefy4kPJFz06ruiLQWNYbt9uhkROivGbsNcL88eH pnqe5gvBO42Quy96D8faREptSLY/mEnUMB9OJrOtWKxts6UNTnag9eL+ccW/zfBHsbOb PSXgaCWbEVUmJeOlc1h6zJf/YNXtVdIbhoFPyuEUBRgcqkaSAD0FwGMK+033tRsjdomV twOCsZjCJBxUWx0cmJO7N/yQpTqK/kC5GCEIPdBUvYCzVyhNljnB+m+C+9da/quVfhX7 /LBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=OtreZKvD; 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 g10si47776pgf.160.2018.02.22.05.33.26; Thu, 22 Feb 2018 05:33:40 -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=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=OtreZKvD; 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 S1753845AbeBVNcP (ORCPT + 99 others); Thu, 22 Feb 2018 08:32:15 -0500 Received: from mail-vk0-f54.google.com ([209.85.213.54]:41054 "EHLO mail-vk0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932395AbeBVNcM (ORCPT ); Thu, 22 Feb 2018 08:32:12 -0500 Received: by mail-vk0-f54.google.com with SMTP id t201so3069642vke.8 for ; Thu, 22 Feb 2018 05:32:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Mw4O3/e4XcDTzK0Qk72i7gDEW+5Y37PNcDtmq/p9au0=; b=OtreZKvDUGHw03ninR8GuGgVL5rs7flDK3WFdBXUlPBz99mFDmgXlXLApEMxgIKxkp 2F7ksYSAq7fi48MAlsIdoQRKnb1TzJU9mvIzhZhODa74f/dfkwDC7E3gXRUb50Usp+aM 1yK7MZS2bYjOBVFU+H/yR7JOHP5m8MbWzHZy6BWlTNbViUD+dykJzO+BVjkwNIcKtkIc RhJtrGrBxJ8IWuD29GyuFYPb8NfhK8bQ4M9P99fcIMGms/EcF4qK992FyMD6wLLIgKdd gqczcDvBzLE1txNOV6qRLALv+HOw77EMrK+ZHlUylzfUDpXi2Kl6FCrrQhkD2jmFLrDR JOpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Mw4O3/e4XcDTzK0Qk72i7gDEW+5Y37PNcDtmq/p9au0=; b=JviQvhz3hd4u00MTU+SCc0Octts3K7DBADE/l5qkVW4pWZax03NHXSwbFbmVrpLRSS TimgmpgzTdiqHZcZsQrHWEMKnoC5boXIzjfxxtQAQ+9haDc41V1JsRwuX3hBSDvafA6p 10oiQRTkec82i3Tc+oCR4XwZY1dwWt+VmRSIc9T/G4QkUQz37G7rnQ/tLLVgWFhOZgTv Pa0h78Dfi4Vbo7SL8PvZfSEAfP55mi5OW/updJ+7j3NkQT5xbtCnWRzWoIybj4LoWcLI nvRcZjUf+2xewSjyPGbUBybP2Sj932l6Bkcmcoio2Vt2ZKT59oV8SDhSb8s1IvH83tdj r7OA== X-Gm-Message-State: APf1xPCw61X6sLlVaZkrNlF5YnjF2ljcBXL/eTo+zsHDdOTFlZA+4NMc q0ydSt1Y8FdgbzqKkgFYL+e96ExdstaCkqrxgFF4uQ== X-Received: by 10.31.252.2 with SMTP id a2mr4963917vki.22.1519306331870; Thu, 22 Feb 2018 05:32:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.60.21 with HTTP; Thu, 22 Feb 2018 05:32:11 -0800 (PST) In-Reply-To: <1519299294.7447.4.camel@pengutronix.de> References: <20180219165837.28913-1-brgl@bgdev.pl> <72cd2af4-ed6b-8c1b-2488-b999976b894a@lechnology.com> <1519123185.3470.5.camel@pengutronix.de> <8ef4b901-f38d-d885-e7bc-657202a2e248@lechnology.com> <1519299294.7447.4.camel@pengutronix.de> From: Bartosz Golaszewski Date: Thu, 22 Feb 2018 14:32:11 +0100 Message-ID: Subject: Re: [PATCH v4] reset: add support for non-DT systems To: Philipp Zabel Cc: David Lechner , Bartosz Golaszewski , LKML , Sekhar Nori , Kevin Hilman Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-02-22 12:34 GMT+01:00 Philipp Zabel : > On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: > [...] >> > In your case the platform code that adds the lookup may be identical to >> > the code that registers the struct reset_controller_dev, but that >> > doesn't have to be the case. I'm not sure how that is supposed to work >> > for the phy framework (I see no platform code adding phy lookups, only >> > drivers). >> > >> In our use case, we would be adding the lookup in the driver rather than >> in the platform code, which is why I am suggesting doing it like the phy >> framework. > > Shouldn't it be the job of the platform code to describe the connections > between reset controller and peripheral module reset > inputs? > > regards > Philipp Am I right to understand that it's ok for drivers to know about the available reset lines on the platform, it's just the associated between these lines and concerned devices that should be done in platform code? Bart