From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Rob Herring <robh@kernel.org>, Andi Shyti <andi.shyti@samsung.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Mark Brown <broonie@kernel.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-spi@vger.kernel.org,
Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH v3 2/7] bindings: spi-samsung: document the clocks and the clock-name property
Date: Mon, 18 Jul 2016 12:30:07 +0200 [thread overview]
Message-ID: <578CAFAF.9060704@samsung.com> (raw)
In-Reply-To: <20160716203044.GA13087@rob-hp-laptop>
On 07/16/2016 10:30 PM, Rob Herring wrote:
>> diff --git a/Documentation/devicetree/bindings/spi/spi-samsung.txt
>> b/Documentation/devicetree/bindings/spi/spi-samsung.txt
>> > index 57d5539..f45c6eb 100644
>> > --- a/Documentation/devicetree/bindings/spi/spi-samsung.txt
>> > +++ b/Documentation/devicetree/bindings/spi/spi-samsung.txt
>> > @@ -24,6 +24,15 @@ Required SoC Specific Properties:
>> > - dma-names: Names for the dma channels. There must be at least one channel
>> > named "tx" for transmit and named "rx" for receive.
>> >
>> > +- clocks: specifies the clock IDs provided to the SPI controller; they are
>> > + required for interacting with the controller itself, for synchronizing the bus
>> > + and as I/O clock (the latter is required by exynos5433 and exynos7).
>> > +
>> > +- clock-names: string names of the clocks in the 'clocks' property; for all the
>> > + the devices the names must be "spi", "spi_busclkN" (where N is determined by
>> > + "samsung,spi-src-clk"), while Exynos5433 should specify a third clock
>
> This sounds like you are describing the configuration of the clocks, not
> the connections. The binding here should list clocks for all possible
> vaules of N as those are all the input clocks to the block.
>
>> > + "spi_ioclk" for the I/O clock.
I agree we should list all possible spi_busclkN, I must admit I might
have introduced some confusion by suggesting wording for clock-names
similar to the above while discussing those things internally. Afterwards
I came to a similar conclusion all possible input clocks should be listed
These will differ depending on the compatible. I checked in documentation
of most of related SoCs and for "samsung,s3c6410-spi" or older compatibles
possible N is 0..2 (PCLK, USBCLK, PLL clock), for "samsung,s5pv210-spi"
and newer possible N is 0 (SCLK_SPI).
It's important to have all the input clocks listed so we have a list
of parent clocks to the SPI controller's internal clocks, should we
ever decide to model them with the clk API.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2016-07-18 10:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 10:02 [PATCH v3 0/7] spi s3c64xx ioclk handling Andi Shyti
2016-07-12 10:02 ` [PATCH v3 1/7] bindings: spi-samsung: add exynos5433 spi compatible Andi Shyti
2016-07-14 16:25 ` Mark Brown
2016-07-16 20:26 ` Rob Herring
2016-07-12 10:02 ` [PATCH v3 2/7] bindings: spi-samsung: document the clocks and the clock-name property Andi Shyti
2016-07-16 20:30 ` Rob Herring
2016-07-18 10:30 ` Sylwester Nawrocki [this message]
2016-07-12 10:02 ` [PATCH v3 3/7] spi: s3c64xx: rename goto labels to meaningful names Andi Shyti
2016-07-12 10:02 ` [PATCH v3 4/7] spi: s3c64xx: use error code from clk_prepare_enable() Andi Shyti
2016-07-12 10:02 ` [PATCH v3 5/7] spi: s3c64xx: add Exynos5433 compatible for ioclk handling Andi Shyti
2016-07-12 10:02 ` [PATCH v3 6/7] spi: s3c64xx: restore removed comments Andi Shyti
2016-07-12 10:02 ` [PATCH v3 7/7] clk: exynos5433: remove CLK_IGNORE_UNUSED flag from SPI clocks Andi Shyti
2016-07-12 22:17 ` Michael Turquette
2016-07-13 2:08 ` Andi Shyti
2016-07-13 9:21 ` Sylwester Nawrocki
2016-07-13 9:54 ` Krzysztof Kozlowski
2016-07-13 12:44 ` Andi Shyti
2016-07-13 21:56 ` Michael Turquette
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=578CAFAF.9060704@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).