From: Kwanghoon Son <kwangson@yahoo.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Kwanghoon Son <k.son@samsung.com>,
s.nawrocki@samsung.com, cw00.choi@samsung.com,
alim.akhtar@samsung.com, mturquette@baylibre.com,
sboyd@kernel.org, robh@kernel.org, conor+dt@kernel.org,
tomasz.figa@gmail.com
Cc: linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: clock: exynosautov9: add dpum clock
Date: Thu, 08 Aug 2024 18:51:34 +0900 [thread overview]
Message-ID: <48be93dc376d115d93b9d79f157e31d7cfedea15.camel@yahoo.com> (raw)
In-Reply-To: <1a7db82e-72ee-496c-a501-54c7dd05cd41@kernel.org>
On Thu, 2024-08-08 at 09:57 +0200, Krzysztof Kozlowski wrote:
> On 30/07/2024 13:15, Kwanghoon Son wrote:
> > Add dpum clock definitions and compatibles.
> >
> > Signed-off-by: Kwanghoon Son <k.son@samsung.com>
> > ---
> > .../clock/samsung,exynosautov9-clock.yaml | 19 +++++++++++++++++++
> > .../dt-bindings/clock/samsung,exynosautov9.h | 11 +++++++++++
> > 2 files changed, 30 insertions(+)
>
> > +
> > + then:
> > + properties:
> > + clocks:
> > + items:
> > + - description: External reference clock (26 MHz)
> > + - description: CMU_DPUM bus clock (from CMU_TOP)
> > +
> > + clock-names:
> > + items:
> > + - const: oscclk
> > + - const: dout_clkcmu_dpum_bus
>
> We need to stop calling input clocks by full name. Rob already pointed
> it out for GS101 and we fixed the approach there. This binding already
> uses above syntax, but I think we can start with proper approach even if
> it leads to inconsistency. So please come with description of this clock
> (not clock name - see GS101) and name, e.g. "bus".
True. I'll look over GS101 more and work in v3.
>
> BTW, in the future, please ping after two weeks or better even: relax,
> and help out by reviewing other patches on the mailing lists in order to
> relieve the burden of maintainers and move your patches higher up the list.
I'll keep in mind.
Thanks for advice.
Kwang.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-08-08 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240730111628epcas1p30976a7c1192749ff7997be5685d52c49@epcas1p3.samsung.com>
2024-07-30 11:15 ` [PATCH v2 0/3] dpum clock support for Exynos Auto v9 SoC Kwanghoon Son
2024-07-30 11:15 ` [PATCH v2 1/3] dt-bindings: clock: exynosautov9: add dpum clock Kwanghoon Son
2024-08-08 7:57 ` Krzysztof Kozlowski
2024-08-08 9:51 ` Kwanghoon Son [this message]
2024-07-30 11:15 ` [PATCH v2 2/3] arm64: dts: exynosautov9: add dpum clock DT nodes Kwanghoon Son
2024-07-30 11:15 ` [PATCH v2 3/3] clk: samsung: exynosautov9: add dpum clock support Kwanghoon Son
2024-08-08 6:26 ` [PATCH v2 0/3] dpum clock support for Exynos Auto v9 SoC Kwanghoon Son
2024-08-08 7:21 ` Krzysztof Kozlowski
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=48be93dc376d115d93b9d79f157e31d7cfedea15.camel@yahoo.com \
--to=kwangson@yahoo.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=k.son@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tomasz.figa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox