Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp477959imm; Tue, 22 May 2018 23:45:37 -0700 (PDT) X-Google-Smtp-Source: AB8JxZr6YCLP/JonREiW9sP56PAVaB2s7tWWQaMKQUViNHvUmgXDG+9galmBxxCS+gfpc+XulSoH X-Received: by 2002:a62:9d89:: with SMTP id a9-v6mr1635139pfk.206.1527057937561; Tue, 22 May 2018 23:45:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527057937; cv=none; d=google.com; s=arc-20160816; b=xiO/u8x/QAdiAPQFUQqElHXlFMc2ta4mGb29ER0vZdZIQwFLHFJDCX7G3GHHwdfWzC +evrGpaYwe8xh8LOZn2oNS5GOZ22bTUj5YQi2ZQBYGPHmyN4pzkYMKiuPh8+mdzSn5Ki hbEi/5fV6zPzWqC5r8qQqFWbC/PZNM6Zn3Ier8AU0/Z41bb+CyVTe7YY8sdZ/QUvU1kT FemrlmHs4HBvMvAcxqbD3nJ5LK7/21Qx5w1eoLNezt+g5tF1sOsjzt4QSSxpiVMGPjeN ZUR3HHGuMpX3YpGFQLNfH20yet/Poyv1hIwKpiNTbKb8xQThpeqpGdfGYUMZmhInugKl y9yg== 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 :arc-authentication-results; bh=eF249B7eAzR9H5roWYKn3MjIJvd38Na4PZQLMv/0jvc=; b=z71qyWDG8OwFCPZzQH9sIgwbIOEW1FtrWVyiQZd62hFiGYAhMvucjwMMT7Ydp6vA+4 hLymDNcMcAum7+7vJjfRzEZLLkt46Bxx0+i2mNf9EMvzYwlZzA/wyVGBFloFmHxs5alt 4ulN32P1IhN+Z0Xt6K2skRQFEURg8rvEHxDQ7WcUWIWWFeO46oupjfpKyhKki8a5oggM 0BcUzOTsjDLKmiWmBoniBbD0yiykVAEJ/Z2pf5En20n3ig1wIk+Ti1c1S88nvA+za9dh IQVfHduJYbtQyq/89sa95/vHL4Q9oK6/7j6KzI/sohMl7hIEbKn0fS1R9BL5sxCYVBaE RBPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Y7YAT0g5; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e6-v6si14273180pgr.374.2018.05.22.23.45.22; Tue, 22 May 2018 23:45:37 -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=@gmail.com header.s=20161025 header.b=Y7YAT0g5; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754207AbeEWGpO (ORCPT + 99 others); Wed, 23 May 2018 02:45:14 -0400 Received: from mail-it0-f68.google.com ([209.85.214.68]:34791 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754114AbeEWGpC (ORCPT ); Wed, 23 May 2018 02:45:02 -0400 Received: by mail-it0-f68.google.com with SMTP id c5-v6so13503572itj.1; Tue, 22 May 2018 23:45:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eF249B7eAzR9H5roWYKn3MjIJvd38Na4PZQLMv/0jvc=; b=Y7YAT0g5WopNayByu8TuD9O/ERUmVVFzYG431s1+ae1QwJ3/TDOIjVMWIOj6VTTL0j 542JaM/McSlB67NFaEjw6vTz6s+yFz1HkDdQ3UL7CSbUWpxkpp4dAr2uQ8Q0mWAdWrQI PjOvCB4HbYka/5cOmvOgIC6Tnpx/jziaeLSXUDD5fJpNdwqOVP1ceSOr9bsGYSYuSzvd C4JKTojEZDzQLF5Cyh/Vck/SMHCZXmlhLtAKWds3cyDlcwIH1O3EqDRoZd8y/f6FUsyh 0Nir0WEPqYC0SS0tGyeKA4QiQ26rxPDtN0hQK2whosKKpoPgoom6054QXX6ZdtO60Xp6 qIKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eF249B7eAzR9H5roWYKn3MjIJvd38Na4PZQLMv/0jvc=; b=ISnJMX5L9TU9P+rtx37XCL9cUEJFzoNZVXrL4KcBgIHRdkGQwsYSQjWRZ4UgOrE4uz PDgDWveEOeuG+8LlVAGwUDFeBA2NFuz+lc8bCENqI7gHgE78ucZj1TQMEfYPDRA1UXy+ h4j5kotLByvLNzNu6FPV+UEjd3hm/jYnPaaVao9pkKJZB6mZJwYQXfPLBETRcVEixr/m cSWaq198akozZM+oLrBoV9YCsJeBGJCy+CArqz528mPEjdIAcJdzV0td5rR5s7XbiNC+ bui31PZwkUnAcZIwuGMmn2sK6w9gvktfga+mEXIf1414ImjIeKeT3IHCfzuOuO1yth4w JUbQ== X-Gm-Message-State: ALKqPwfCGQrRYXzbouSvk0bAGjvq+CfMskZapS9cpFpI5vuQkEjmOq8g Ya6KESuYayBIroh1Hjmgnqwz04TBUv9VqUTV0iY= X-Received: by 2002:a24:17c2:: with SMTP id 185-v6mr4115121ith.45.1527057901699; Tue, 22 May 2018 23:45:01 -0700 (PDT) MIME-Version: 1.0 References: <1526983321-41949-1-git-send-email-michel.pollet@bp.renesas.com> <1526983321-41949-3-git-send-email-michel.pollet@bp.renesas.com> In-Reply-To: From: M P Date: Wed, 23 May 2018 07:44:50 +0100 Message-ID: Subject: Re: [PATCH v6 2/6] dt-bindings: Add the rzn1-clocks.h file To: geert@linux-m68k.org Cc: michel.pollet@bp.renesas.com, linux-renesas-soc@vger.kernel.org, horms@verge.net.au, Phil Edworthy , buserror+upstream@gmail.com, magnus.damm@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com, mturquette@baylibre.com, sboyd@kernel.org, geert+renesas@glider.be, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org 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, 22 May 2018 at 19:44, Geert Uytterhoeven wrote: > Hi Michel, > On Tue, May 22, 2018 at 12:01 PM, Michel Pollet > wrote: > > This adds the constants necessary to use the renesas,rzn1-clocks driver. > > > > Signed-off-by: Michel Pollet > Thanks for your patch! > > --- > > include/dt-bindings/clock/rzn1-clocks.h | 187 ++++++++++++++++++++++++++++++++ > > 1 file changed, 187 insertions(+) > > create mode 100644 include/dt-bindings/clock/rzn1-clocks.h > > > > diff --git a/include/dt-bindings/clock/rzn1-clocks.h b/include/dt-bindings/clock/rzn1-clocks.h > > new file mode 100644 > > index 0000000..8a73db2 > > --- /dev/null > > +++ b/include/dt-bindings/clock/rzn1-clocks.h > Given this is part of the DT ABI, and there exist multiple different RZ/N1 > SoCs (and there are probably planned more), I wouldn't call this header > file "rzn1-clocks.h", but e.g. "r9a06g032-clocks.h". Actually, no, there already are two r906g03X devices that will work perfectly fine with this driver. We had that discussion before, and you insist and me removing mentions of the rzn1 everywhere, however, this applies to *two* devices already, and I'm supposed to upstream support for them. I can't rename r9g06g032 because it is *inexact* that's why it's called rzn1. So unless you let me call it r9a06g0xx-clocks.h (which i know you won't as per multiple previous discussions) this can't be called r9a06g032 because it won't be fit for my purpose when I try to bring back the RZ/N1S into the picture. There are minor difference to clocking, I don't know if Renesas plans to release any more rzn1's in this series, but my little finger tells me this isn't the case. But regardless of what we plan, Marketing will screw it up. Cheers, Michel > > @@ -0,0 +1,187 @@ > > +/* SPDX-License-Identifier: GPL-2.0 */ > > +/* > > + * RZ/N1 clock IDs > > + * > > + * Copyright (C) 2018 Renesas Electronics Europe Limited > > + * > > + * Michel Pollet , > > + * Derived from zx-reboot.c > > + */ > > + > > +#ifndef __DT_BINDINGS_RZN1_CLOCK_H__ > > +#define __DT_BINDINGS_RZN1_CLOCK_H__ > > + > > +#define RZN1_CLKOUT 0 > Similar for the RZN1 prefix. > I'll look at the actual list of clocks later... > Gr{oetje,eeting}s, > Geert > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds