Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4671101yba; Wed, 8 May 2019 00:21:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqy8xw/IaeV2Mw2dYapmSeFBObsn+eaLNYvlUPCOMpwgGB6/hQD8rB1PvnZFjq84yUVkkH2U X-Received: by 2002:a17:902:9a03:: with SMTP id v3mr46872545plp.27.1557300069562; Wed, 08 May 2019 00:21:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557300069; cv=none; d=google.com; s=arc-20160816; b=ouoz93m2D1eCTil4jzmAiiZtEoQdBnL4saUPkuIexmGRS/whTBe6WDI4i71271kT2W 159Fbpfv3Bgonu6V+YGkZ3O+1ucYvS1/72y/+pl1/bcjsjbQ35YDyCahjn4bxjQUv6rc fElQprdStwMSUuMRonk4bQyG+dar27Qr323EZU2RLFOxlHXkJug50KXqWC3Ev8yhvZZ6 IpgpwLA00BnmEycJWC3gcHsJkApv7GAQ22TG0ulQG7dp4D18UNsNKOaLmtQCGaclqL8L ImT+DT1ur7ELOJEympBdJdAAa+wIJnnp2x0z4T9gSnb/lIymMD1AvK+XUbYLPivS+snY h52A== 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 :in-reply-to:references:mime-version:dkim-signature; bh=5s82mRz37GOU+IcMp3MyKMCbLiU1C7ZcUVGcNhpH5lw=; b=SYlvYZvGlPM2HAXIFlsfdOVBSpfxBAlaIv+nz0o9wp0/33Q57aDjbTj6N6Y33dJHWx XF/sq16S6jugMnM7CjMnpYMxPzC9isYVze/F1YHJL1a3EBW6jLXU/Oyww7dgI2/cGPGB vdG6N2xe2Kst/adRCMecjNAZgu3RQcjogICKnafdNbH4dAyYB5G0ry7HK514EaB76EMo e+//p8RszRvGOywURKApxXZLzYanJL2FIerOpSb8S8Ux9SQv5JqLh2DmkaA5F1A47sqn 2EeLC0Ob5cM3bQo2m1wxrD3coTWrbVssMx3aIV95NeRr8AHCNRsND/R2yElYg2L4KX9x xcXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=E11ak32V; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cm8si24939322plb.159.2019.05.08.00.20.52; Wed, 08 May 2019 00:21:09 -0700 (PDT) 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=@kernel.org header.s=default header.b=E11ak32V; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726816AbfEHHT4 (ORCPT + 99 others); Wed, 8 May 2019 03:19:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:44944 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725880AbfEHHTz (ORCPT ); Wed, 8 May 2019 03:19:55 -0400 Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 59B94216F4; Wed, 8 May 2019 07:19:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557299994; bh=5s82mRz37GOU+IcMp3MyKMCbLiU1C7ZcUVGcNhpH5lw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=E11ak32VdWO0HCXiaIpYYhSLkUOVSzGtt7C+duhsSnuQq1m6wnKsF9DbzeBfbNc9m c+eps5T9ZXj80o34QZ7K1C60+YBFBvOXxp+1tp7n1xRdGWiKGvRd2dToNEktE2wC/i kYMiUUwgXOFEreKWIcgOHyJNFdB9STkqkxCRVvKk= Received: by mail-lf1-f48.google.com with SMTP id v18so11544612lfi.1; Wed, 08 May 2019 00:19:54 -0700 (PDT) X-Gm-Message-State: APjAAAV6cVVNY1Yeg2NHtq16WfIZ7SLNvj/DVONY3mXPRaILrcALKAQT EQfbE8ylEGBlIs0A/nFaGKPeIAXJbUWlLT+JHsU= X-Received: by 2002:ac2:4992:: with SMTP id f18mr5172113lfl.154.1557299992587; Wed, 08 May 2019 00:19:52 -0700 (PDT) MIME-Version: 1.0 References: <1557155521-30949-1-git-send-email-l.luba@partner.samsung.com> <1557155521-30949-8-git-send-email-l.luba@partner.samsung.com> <20190507170422.GA25179@bogus> In-Reply-To: <20190507170422.GA25179@bogus> From: Krzysztof Kozlowski Date: Wed, 8 May 2019 09:19:40 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 07/13] dt-bindings: memory-controllers: add Exynos5422 DMC device description To: Rob Herring Cc: Lukasz Luba , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" , =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, Chanwoo Choi , kyungmin.park@samsung.com, Marek Szyprowski , s.nawrocki@samsung.com, myungjoo.ham@samsung.com, keescook@chromium.org, tony@atomide.com, jroedel@suse.de, treding@nvidia.com, digetx@gmail.com, willy.mh.wolff.ml@gmail.com 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 On Tue, 7 May 2019 at 19:04, Rob Herring wrote: > > +- devfreq-events : phandles of the PPMU events used by the controller. > > +- samsung,syscon-chipid : phandle of the ChipID used by the controller. > > +- samsung,syscon-clk : phandle of the clock register set used by the controller. > > Looks like a hack. Can't you get this from the clocks property? What is > this for? Hi Rob, Lukasz uses these two syscon regmaps to read certain registers. For chipid he reads it to check the size of attached memory (only 2 GB version is supported). This indeed looks like a hack. However the second regmap (clk) is needed to get the timing data from registers from DMC clock driver address space. These are registers with memory timing so their data is not exposed anyway in common clk framework. Best regards, Krzysztof