From: Stephen Boyd <sboyd@kernel.org>
To: "Kim, Cheol Yong" <cheol.yong.kim@linux.intel.com>,
"Tanwar, Rahul" <rahul.tanwar@linux.intel.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.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
Subject: Re: [PATCH v1 1/2] clk: intel: Add CGU clock driver for a new SoC
Date: Mon, 16 Sep 2019 11:36:18 -0700 [thread overview]
Message-ID: <20190916183619.50926206C2@mail.kernel.org> (raw)
In-Reply-To: <4e1ddc50-7ae3-3ba9-7e41-80a834fa2dbf@linux.intel.com>
Quoting Kim, Cheol Yong (2019-09-09 07:16:29)
>
> I've discussed internally the amount of efforts to create a reusable
> regmap clock driver which might be reused by other companies too.
>
> 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
> put such a big efforts.
>
> Stephan,
>
> It seems you don't like both meson/qcom regmap clock implementation.
>
> What is your opinion for our current CGU clock driver implementation?
>
>
If you're not going to use regmap in CGU then it doesn't matter to try
to consolidate the regmap clk implementations.
next prev parent reply other threads:[~2019-09-16 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:00 [PATCH v1 0/2] clk: intel: Add a new driver for a new clock controller IP Rahul Tanwar
2019-08-28 7:00 ` [PATCH v1 1/2] clk: intel: Add CGU clock driver for a new SoC Rahul Tanwar
2019-08-28 15:09 ` Andy Shevchenko
2019-09-02 7:43 ` Tanwar, Rahul
2019-09-02 12:20 ` Andy Shevchenko
2019-09-02 12:24 ` Andy Shevchenko
2019-12-06 4:39 ` Tanwar, Rahul
2019-12-07 14:57 ` Andy Shevchenko
2019-12-24 3:04 ` Stephen Boyd
2019-09-02 22:20 ` Martin Blumenstingl
2019-09-03 9:54 ` Tanwar, Rahul
2019-09-03 18:53 ` Martin Blumenstingl
2019-09-04 8:03 ` Tanwar, Rahul
2019-09-05 20:47 ` Martin Blumenstingl
2019-09-09 14:16 ` Kim, Cheol Yong
2019-09-16 18:36 ` Stephen Boyd [this message]
2019-09-03 23:54 ` Stephen Boyd
2019-08-28 7:00 ` [PATCH v1 2/2] dt-bindings: clk: intel: Add bindings document & header file for CGU Rahul Tanwar
2019-12-19 16:33 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190916183619.50926206C2@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=cheol.yong.kim@linux.intel.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=rahul.tanwar@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=yixin.zhu@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.