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;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <4e1ddc50-7ae3-3ba9-7e41-80a834fa2dbf@linux.intel.com>
References: <6a3c26bc6e25d883686287883528dbde30725922.1566975410.git.rahul.tanwar@linux.intel.com> <20190902222015.11360-1-martin.blumenstingl@googlemail.com> <d9e96dab-96be-0c14-b7af-e1f2dc07ebd2@linux.intel.com> <CAFBinCARQJ7q9q3r6c6Yr2SD0Oo_Drah-kxss3Obs-g=B1M28A@mail.gmail.com> <b7920723-1df2-62df-61c7-98c3a1665aa1@linux.intel.com> <CAFBinCA+J-HnXfRnquqviXvX0Jo84hoLC9=_uHbyWKZycwyAFw@mail.gmail.com> <4e1ddc50-7ae3-3ba9-7e41-80a834fa2dbf@linux.intel.com>
Cc:     andriy.shevchenko@intel.com, cheol.yong.kim@intel.com,
        linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
        mark.rutland@arm.com, mturquette@baylibre.com,
        qi-ming.wu@intel.com, rahul.tanwar@intel.com, robh+dt@kernel.org,
        robh@kernel.org, yixin.zhu@linux.intel.com
To:     "Kim, Cheol Yong" <cheol.yong.kim@linux.intel.com>,
        "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>,
        Martin Blumenstingl <martin.blumenstingl@googlemail.com>
From:   Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v1 1/2] clk: intel: Add CGU clock driver for a new SoC
User-Agent: alot/0.8.1
Date:   Mon, 16 Sep 2019 11:36:18 -0700
Message-Id: <20190916183619.50926206C2@mail.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Kim, Cheol Yong (2019-09-09 07:16:29)
>=20
> I've discussed internally the amount of efforts to create a reusable=20
> regmap clock driver which might be reused by other companies too.
>=20
> It seems it requires significant efforts for implementation/tests. As we =

> don't plan to support our old SOCs for now, I'm not sure if we need to=20
> put such a big efforts.
>=20
> Stephan,
>=20
> It seems you don't like both meson/qcom regmap clock implementation.
>=20
> What is your opinion for our current CGU clock driver implementation?
>=20
>=20

If you're not going to use regmap in CGU then it doesn't matter to try
to consolidate the regmap clk implementations.