public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Vladimir Zapolskiy <vz@mleia.com>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 8/9] dt-bindings: rtc: stmp3xxx-rtc: convert to dtschema
Date: Tue, 9 Apr 2024 11:22:02 +0200	[thread overview]
Message-ID: <89e7db2d-1de0-4e2e-a2d2-f00d45399b11@gmail.com> (raw)
In-Reply-To: <f0467c4f-45e2-4cae-b1b5-3867e5b9bf08@linaro.org>

On 4/9/24 09:40, Krzysztof Kozlowski wrote:
> On 08/04/2024 17:53, Javier Carrasco wrote:
>> Convert existing binding to dtschema to support validation.
>>
>> The 'fsl,imx28-rtc' compatible is currently not supported, and it is
>> only referenced in this binding and in nxp/mxs/imx28.dtsi. Therefore,
>> that compatible has been dropped, which triggers a warning when testing
>> the DT against the new binding.
> 
> Instead document missing compatibles and mention this in commit msg.
> 


There is no driver that will match 'fsl,imx28-rtc', only
'fsl,stmp3xxx-rtc', so I am not sure how to document the missing
compatible in a sensible way. My first suggestion to account for
undocumented strings would be:

  compatible:
    oneOf:
      - items:
          - enum:
              - fsl,imx23-rtc
              - fsl,imx28-rtc
          - const: fsl,stmp3xxx-rtc
      - const: fsl,stmp3xxx-rtc

Any suggestions or improvements?

>>
>> There is another reference to fsl,stmp3xxx-rtc in nxp/mxs/imx23.dtsi,
>> where another unsupported compatible 'fsl,imx23-rtc' is used, and the
>> same problem would arise when testing the file against the new binding.
> 
> Please write concise messages... you have to paragraphs about the same?
> What is the difference here?
> 
The difference is that 'fsl,imx23-rtc' was not even mentioned in any
binding, and it can only be found in imx23.dtsi. 'fsl,imx28-rtc' was
indeed mentioned in the txt binding.

My understanding after your comment is that we should gather
undocumented compatibles and add them to the bindings they would belong
to,no matter if they are used anywhere or not. I added this one to the
suggestion above as well.

>>
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
>> ---
>>  .../devicetree/bindings/rtc/fsl,stmp3xxx-rtc.yaml  | 45 ++++++++++++++++++++++
>>  .../devicetree/bindings/rtc/stmp3xxx-rtc.txt       | 21 ----------
>>  2 files changed, 45 insertions(+), 21 deletions(-)
>>
> 
> 
> Best regards,
> Krzysztof
> 

Best regards,
Javier Carrasco

  reply	other threads:[~2024-04-09  9:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 15:53 [PATCH 0/9] rtc: convert multiple bindings into dtschema Javier Carrasco
2024-04-08 15:53 ` [PATCH 1/9] dt-bindings: rtc: orion-rtc: move to trivial-rtc Javier Carrasco
2024-04-09  7:31   ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 2/9] dt-bindings: rtc: google,goldfish-rtc: " Javier Carrasco
2024-04-09  7:32   ` Krzysztof Kozlowski
2024-04-16 22:45   ` kernel test robot
2024-04-17  8:19     ` Javier Carrasco
2024-04-08 15:53 ` [PATCH 3/9] dt-bindings: rtc: lpc32xx-rtc: " Javier Carrasco
2024-04-09  7:34   ` Krzysztof Kozlowski
2024-04-09  8:52     ` Javier Carrasco
2024-04-09  9:40       ` Krzysztof Kozlowski
2024-04-09 12:11       ` Alexandre Belloni
2024-04-08 15:53 ` [PATCH 4/9] dt-bindings: rtc: maxim,ds1742: " Javier Carrasco
2024-04-09  7:35   ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 5/9] dt-bindings: rtc: rtc-aspeed: " Javier Carrasco
2024-04-09  7:36   ` Krzysztof Kozlowski
2024-04-09 11:53   ` Andrew Jeffery
2024-04-08 15:53 ` [PATCH 6/9] dt-bindings: rtc: pxa-rtc: convert to dtschema Javier Carrasco
2024-04-09  7:37   ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 7/9] dt-bindings: rtc: spear-rtc: move to trivial-rtc Javier Carrasco
2024-04-09  7:37   ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 8/9] dt-bindings: rtc: stmp3xxx-rtc: convert to dtschema Javier Carrasco
2024-04-09  7:40   ` Krzysztof Kozlowski
2024-04-09  9:22     ` Javier Carrasco [this message]
2024-04-09  9:42       ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 9/9] dt-bindings: rtc: via,vt8500-rtc: move to trivial-rtc Javier Carrasco
2024-04-09  7:40   ` Krzysztof Kozlowski
2024-04-09 10:26 ` [PATCH 0/9] rtc: convert multiple bindings into dtschema Alexandre Belloni
2024-04-09 12:02   ` Javier Carrasco

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=89e7db2d-1de0-4e2e-a2d2-f00d45399b11@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh@kernel.org \
    --cc=vz@mleia.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