mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Rob Herring" <robh@kernel.org>
Cc: "Lee Jones" <lee@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"paulburton@kernel.org" <paulburton@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v2 6/8] dt-bindings: mfd: Add img,boston-platform-regs
Date: Thu, 13 Jun 2024 20:31:46 +0100	[thread overview]
Message-ID: <bbbd52c2-aaf2-4777-bee4-855d805923b5@app.fastmail.com> (raw)
In-Reply-To: <20240613190429.GA2309072-robh@kernel.org>



在2024年6月13日六月 下午8:04,Rob Herring写道:
> On Wed, Jun 12, 2024 at 12:56:25PM +0100, Jiaxun Yang wrote:
>> This compatible has been used in arch/mips/boot/dts/img/boston.dts
>> for a while but never documented properly.
>> 
>> Write a new binding for this device.
>> This also covers old img,boston-clock binding so remove that binding.
>> 
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>> ---
>>  .../devicetree/bindings/clock/img,boston-clock.txt | 31 ---------
>>  .../bindings/mfd/img,boston-platform-regs.yaml     | 74 ++++++++++++++++++++++
>>  2 files changed, 74 insertions(+), 31 deletions(-)
>> 
>> diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt b/Documentation/devicetree/bindings/clock/img,boston-clock.txt
>> deleted file mode 100644
>> index 7bc5e9ffb624..000000000000
>> --- a/Documentation/devicetree/bindings/clock/img,boston-clock.txt
>> +++ /dev/null
>> @@ -1,31 +0,0 @@
>> -Binding for Imagination Technologies MIPS Boston clock sources.
>> -
>> -This binding uses the common clock binding[1].
>> -
>> -[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
>> -
>> -The device node must be a child node of the syscon node corresponding to the
>> -Boston system's platform registers.
>> -
>> -Required properties:
>> -- compatible : Should be "img,boston-clock".
>> -- #clock-cells : Should be set to 1.
>> -  Values available for clock consumers can be found in the header file:
>> -    <dt-bindings/clock/boston-clock.h>
>> -
>> -Example:
>> -
>> -	system-controller@17ffd000 {
>> -		compatible = "img,boston-platform-regs", "syscon";
>> -		reg = <0x17ffd000 0x1000>;
>> -
>> -		clk_boston: clock {
>> -			compatible = "img,boston-clock";
>> -			#clock-cells = <1>;
>> -		};
>> -	};
>> -
>> -	uart0: uart@17ffe000 {
>> -		/* ... */
>> -		clocks = <&clk_boston BOSTON_CLK_SYS>;
>> -	};
>> diff --git a/Documentation/devicetree/bindings/mfd/img,boston-platform-regs.yaml b/Documentation/devicetree/bindings/mfd/img,boston-platform-regs.yaml
>> new file mode 100644
>> index 000000000000..bf94de38a89f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/img,boston-platform-regs.yaml
>> @@ -0,0 +1,74 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mfd/img,boston-platform-regs.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Imagination Technologies Boston Platform Registers
>> +
>> +maintainers:
>> +  - Jiaxun Yang <jiaxun.yang@flygoat.com>
>> +
>> +properties:
>> +  compatible:
>> +    items:
>> +      - const: img,boston-platform-regs
>> +      - const: syscon
>> +      - const: simple-mfd
>
> Why did you add 'simple-mfd'? That's not what is in use.
>

U-Boot needs this to probe sub-nodes such as reboot and clock :-(

I had updated dts in an earlier patch of this series.

Thanks
>>

-- 
- Jiaxun

  reply	other threads:[~2024-06-13 19:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 11:56 [PATCH v2 0/8] MIPS: Boston: Fix syscon devicetree binding and node Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 1/8] MIPS: dts: Boston: Add simple-mfd compatible for syscon Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 2/8] MIPS: dts: Boston: Move syscon-reboot node under syscon Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 3/8] MIPS: dts: Boston: Remove unused #interrupt-cells Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 4/8] MIPS: dts: Boston: Add model property Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 5/8] MIPS: dts: Boston: Rename uart node Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 6/8] dt-bindings: mfd: Add img,boston-platform-regs Jiaxun Yang
2024-06-13 19:04   ` Rob Herring
2024-06-13 19:31     ` Jiaxun Yang [this message]
2024-06-12 11:56 ` [PATCH v2 7/8] du-bindings: mips: cpu: Add img,mips compatible Jiaxun Yang
2024-06-12 16:39   ` Conor Dooley
2024-06-12 16:59     ` Jiaxun Yang
2024-06-13 18:59       ` Rob Herring
2024-06-13 19:40         ` Jiaxun Yang
2024-06-15 12:28           ` Conor Dooley
2024-06-15 19:16             ` Jiaxun Yang
2024-06-19 18:13               ` Conor Dooley
2024-06-12 11:56 ` [PATCH v2 8/8] dt-bindings: mips: img: Add devices binding Jiaxun Yang
2024-06-12 16:43   ` Conor Dooley
2024-06-12 16:57     ` Jiaxun Yang
2024-06-12 16:59       ` Conor Dooley
2024-06-13 18:56   ` Rob Herring

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=bbbd52c2-aaf2-4777-bee4-855d805923b5@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.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

Powered by JetHome