From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: i2c: exynos5: Add samsung,exynos8895-hsi2c compatible
Date: Tue, 17 Dec 2024 11:31:30 +0200 [thread overview]
Message-ID: <17fbfcdd-8b79-4907-a4c8-798da0ef0526@gmail.com> (raw)
In-Reply-To: <69fd1dbc-a29f-488c-a30f-7e5ea8f01a23@kernel.org>
On 12/17/24 11:26, Krzysztof Kozlowski wrote:
> On 17/12/2024 10:08, Ivaylo Ivanov wrote:
>>>>>> - items:
>>>>>> - enum:
>>>>>> @@ -94,9 +95,28 @@ allOf:
>>>>>> - clock-names
>>>>>>
>>>>>> else:
>>>>>> - properties:
>>>>>> - clocks:
>>>>>> - maxItems: 1
>>>>>> + if:
>>>>>> + properties:
>>>>>> + compatible:
>>>>>> + contains:
>>>>>> + enum:
>>>>>> + - samsung,exynos8895-hsi2c
>>>>>> +
>>>>>> + then:
>>>>>> + properties:
>>>>>> + clocks:
>>>>> Missing minItems
>>>>>
>>>>>> + maxItems: 2
>>>>>> +
>>>>>> + clock-names:
>>>>> Ditto
>>>>>
>>>>>> + maxItems: 2
>>>>>> +
>>>>>> + required:
>>>>>> + - clock-names
>>>>> I don't understand why do you need second, same branch in if, basically
>>>> Because, as I stated in the commit message, we have HSI2C controllers
>>>> both implemented in USIv1 blocks and outside. These that are a part of
>>> On Exynos8895? Where? With the same compatible?
>> hsi2c_0 which has a clock from BUSC and hsi2c_1 to hsi2c_4 which use clocks
>> from PERIC1 (CLK_GOUT_PERIC1_HSI2C_CAM{0,1,2,3}_IPCLK). Why would
>> they need a different compatible though? It's functionally the same i2c design
>> as the one implemented in USIv1 blocks.
> If one block is part of USI and other not, they might not be the same
> I2C blocks, even if interface is similar. If they were the same or even
> functionally the same, they would have the same clock inputs. However
I see, so in such case I should make samsung,exynos8895-hsi2c-nonusi or
something like that?
> user manual also suggests that there is only one clock, not two (for
> both cases), so they could be functionally equivalent but then number of
> clocks looks incorrect.
That'd be weird. Both according to downstream and upstream clk driver,
for the USI-implemented i2cs we have a pclk and an sclk_usi.
Best regards,
Ivo.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2024-12-17 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 22:04 [PATCH v1 0/2] i2c: exynos5: Add support for Exynos8895 SoC Ivaylo Ivanov
2024-12-14 22:04 ` [PATCH v1 1/2] dt-bindings: i2c: exynos5: Add samsung,exynos8895-hsi2c compatible Ivaylo Ivanov
2024-12-16 8:44 ` Krzysztof Kozlowski
2024-12-16 20:59 ` Ivaylo Ivanov
2024-12-17 5:24 ` Krzysztof Kozlowski
2024-12-17 9:08 ` Ivaylo Ivanov
2024-12-17 9:26 ` Krzysztof Kozlowski
2024-12-17 9:31 ` Ivaylo Ivanov [this message]
2024-12-17 9:43 ` Krzysztof Kozlowski
2024-12-17 10:04 ` Ivaylo Ivanov
2024-12-18 9:22 ` Krzysztof Kozlowski
2024-12-18 9:30 ` Ivaylo Ivanov
2024-12-17 17:42 ` Markuss Broks
2024-12-14 22:04 ` [PATCH v1 2/2] i2c: exynos5: Add support for Exynos8895 SoC Ivaylo Ivanov
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=17fbfcdd-8b79-4907-a4c8-798da0ef0526@gmail.com \
--to=ivo.ivanov.ivanov1@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
/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).