devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	dinguyen@kernel.org, marex@denx.de, s.trumtrar@pengutronix.de,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 12/23] ARM: socfpga: dts: add a10 clock binding yaml
Date: Thu, 24 Oct 2024 08:24:41 +0200	[thread overview]
Message-ID: <cdc7032b-4d09-40dc-86a7-16d244517d11@kernel.org> (raw)
In-Reply-To: <CAFXKEHZOPioES4guqjco+BE7i=Eqe2DdHiUxAksBCZm7nx1Rog@mail.gmail.com>

On 24/10/2024 08:10, Lothar Rubusch wrote:
> On Mon, Oct 21, 2024 at 9:05 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Sun, Oct 20, 2024 at 07:40:17PM +0000, Lothar Rubusch wrote:
>>> Convert content of the altera socfpga.txt to match clock bindings for
>>> the Arria10 SoC devicetrees. Currently all altr,* bindings appear as
>>> error at dtbs_check, since these bindings are only written in .txt
>>> format.
>>>
>>
>> Please use subject prefixes matching the subsystem. You can get them for
>> example with 'git log --oneline -- DIRECTORY_OR_FILE' on the directory
>> your patch is touching. For bindings, the preferred subjects are
>> explained here:
>> https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
>>
>>> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
>>> ---
>>>  .../bindings/clock/altr,socfpga-a10.yaml      | 107 ++++++++++++++++++
>>>  1 file changed, 107 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/clock/altr,socfpga-a10.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/clock/altr,socfpga-a10.yaml b/Documentation/devicetree/bindings/clock/altr,socfpga-a10.yaml
>>> new file mode 100644
>>> index 000000000..795826f53
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/clock/altr,socfpga-a10.yaml
>>> @@ -0,0 +1,107 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/clock/altr,socfpga-a10.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Device Tree Clock bindings for Altera's SoCFPGA platform
>>
>> This wasn't tested or you have some very, very old dtschema.
>>
>>
>>> +
>>> +maintainers:
>>> +  - TODO
>>
>> We should not be taking unmaintained stuff.
>>
> 
> This is just a trigger here. Basically, I have no probelm in placing
> my own name here. AFAIR Mr. Dinh Nguyen has his name on the other
> intel/altera related files, so I'm not sure who decides that. Please
> let me know.
> 
> Basically this particular patch is related to my initial questions
> (cover letter):
> 1.) Documentation/devicetree/bindings:
> Executing the following find...
> $ find ./Documentation/devicetree/bindings -name socfpga-\*.txt
> ...shows 4 text files describing "altr," bindings. I sketch-implemented
> the clock binding and could reduce some of my dtbs_check warnings. So, my
> questions is, if this is the right way? Shall I try to write .yaml files
> for all 4 of them, too? Related to that, who will be maintainer?

Whoever is interested in that hardware. Platform maintainer, device
maintainer.

> 
> 2.) Some bindings, e.g. the Silabs clock generator seem to have no
> driver, thus show up as warning:
>     compatible = "silabs,si5338";
> IMHO it is most likely rather to be probed/loaded in the SPL of the
> bootloader. Is it problematic to keep those declarations (showing up as
> warning in dtbs_check) or how to deal with them?

Sorry, I don't get the problem.

> 
> 3.) Please, give me some feedback if the DT and binding adjustments are
> going into total wrong direction, or where I may do better. If it is ok,
> and acceptable, or what is still missing. I tried to split them, to
> allow for better single integration / discussion let me know if this is
> ok, too.

I still don't understand. Nothing here is different than with every
other platform.

> 
> 
>>> +
>>> +description:
>>> +  This binding uses the common clock binding[1].
>>> +
>>> +  [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
>>
>> Drop description or describe the hardware.
> 
> Ok (the description was taken as content from the corresponding .txt file)

What corresponding txt file? You are adding new binding. Are you saying
you duplicated bindings instead of doing conversion?

git log -p -- Documentation/devicetree | grep -i convert



Best regards,
Krzysztof


  reply	other threads:[~2024-10-24  6:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 19:40 [PATCHv2 00/23] Add Enclustra Arria10 and Cyclone5 SoMs Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 01/23] ARM: dts: socfpga: fix typo Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 02/23] ARM: dts: socfpga: align bus name with bindings Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 03/23] ARM: dts: socfpga: align dma name with binding Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 04/23] ARM: dts: socfpga: align fpga-region name Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 05/23] ARM: dts: socfpga: add label to clock manager Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 06/23] ARM: dts: socfpga: add missing cells properties Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 07/23] ARM: dts: socfpga: fix missing ranges Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 08/23] ARM: dts: socfpga: add clock-frequency property Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 09/23] ARM: dts: socfpga: add ranges property to sram Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 10/23] ARM: dts: socfpga: remove arria10 reset-names Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 11/23] ARM: socfpga: dts: add compatibility for arria10 Lothar Rubusch
2024-10-21  7:05   ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 12/23] ARM: socfpga: dts: add a10 clock binding yaml Lothar Rubusch
2024-10-20 22:21   ` Rob Herring (Arm)
2024-10-21  7:04   ` Krzysztof Kozlowski
2024-10-24  6:10     ` Lothar Rubusch
2024-10-24  6:24       ` Krzysztof Kozlowski [this message]
2024-10-25  6:59         ` Lothar Rubusch
2024-10-25  8:01           ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 13/23] ARM: dts: socfpga: add Enclustra boot-mode dtsi Lothar Rubusch
2024-10-23 17:20   ` Ahmad Fatoum
2024-10-24  6:15     ` Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 14/23] ARM: dts: socfpga: add Enclustra base-board dtsi Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 15/23] ARM: dts: socfpga: add Enclustra Mercury SA1 Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 16/23] dt-bindings: altera: " Lothar Rubusch
2024-10-21  7:47   ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 17/23] ARM: dts: socfpga: add Enclustra Mercury+ SA2 Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 18/23] dt-bindings: altera: add binding for " Lothar Rubusch
2024-10-21  7:47   ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 19/23] ARM: dts: socfpga: add Mercury AA1 combinations Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 20/23] dt-bindings: altera: " Lothar Rubusch
2024-10-21  7:48   ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 21/23] ARM: dts: socfpga: removal of generic PE1 dts Lothar Rubusch
2024-10-20 19:40 ` [PATCHv2 22/23] dt-bindings: altera: " Lothar Rubusch
2024-10-21  7:48   ` Krzysztof Kozlowski
2024-10-20 19:40 ` [PATCHv2 23/23] ARM: dts: socfpga: add Enclustra SoM dts files Lothar Rubusch
2024-10-21 17:58 ` [PATCHv2 00/23] Add Enclustra Arria10 and Cyclone5 SoMs Rob Herring (Arm)

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=cdc7032b-4d09-40dc-86a7-16d244517d11@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=l.rubusch@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=robh@kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    /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).