devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Varshini.Rajendran@microchip.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	Nicolas.Ferre@microchip.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 25/27] ARM: dts: at91: sam9x7: add device tree for SoC
Date: Tue, 27 Aug 2024 14:48:25 +0200	[thread overview]
Message-ID: <5fbc815f-d52e-437d-bdc3-c61f365e9d1c@kernel.org> (raw)
In-Reply-To: <bf77fe95-0982-4605-a493-25c889e81639@microchip.com>

On 27/08/2024 11:50, Varshini.Rajendran@microchip.com wrote:
> Hi Krzysztof,
> 
> Apologies for the delay in response.
> 
> On 31/07/24 2:00 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 29/07/2024 09:09, Varshini Rajendran wrote:
>>> Add device tree file for SAM9X7 SoC family.
>>>
>>> Co-developed-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com>
>>
>> ...
>>
>>> +
>>> +             can1: can@f8004000 {
>>> +                     compatible = "bosch,m_can";
>>> +                     reg = <0xf8004000 0x100>, <0x300000 0xbc00>;
>>> +                     reg-names = "m_can", "message_ram";
>>> +                     interrupts = <30 IRQ_TYPE_LEVEL_HIGH 0>,
>>> +                                  <69 IRQ_TYPE_LEVEL_HIGH 0>;
>>> +                     interrupt-names = "int0", "int1";
>>> +                     clocks = <&pmc PMC_TYPE_PERIPHERAL 30>, <&pmc PMC_TYPE_GCK 30>;
>>> +                     clock-names = "hclk", "cclk";
>>> +                     assigned-clocks = <&pmc PMC_TYPE_CORE PMC_UTMI>, <&pmc PMC_TYPE_GCK 30>;
>>> +                     assigned-clock-rates = <480000000>, <40000000>;
>>> +                     assigned-clock-parents = <&pmc PMC_TYPE_CORE PMC_UTMI>, <&pmc PMC_TYPE_CORE PMC_UTMI>;
>>> +                     bosch,mram-cfg = <0x7800 0 0 64 0 0 32 32>;
>>> +                     status = "disabled";
>>> +             };
>>> +
>>> +             tcb: timer@f8008000 {
>>> +                     compatible = "microchip,sam9x7-tcb","atmel,sama5d2-tcb", "simple-mfd", "syscon";
>>
>> Why this is simple-mfd without children?
> 
> The tcb node will have each TC (Timer Counter) Block as a child when it 
> is configured to be used as either one of the following modes Timer or 
> Counter / Capture / PWM.

And where are these children? What does it mean "will have", in context
when? DTS is static, if you do not have here children then this is not a
simple-mfd.

Best regards,
Krzysztof


  reply	other threads:[~2024-08-27 12:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  6:56 [PATCH v6 00/27] Add support for sam9x7 SoC family Varshini Rajendran
2024-07-29  7:05 ` [PATCH v6 01/27] dt-bindings: atmel-sysreg: add sam9x7 Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 02/27] dt-bindings: mfd: syscon: add microchip's sam9x7 sfr Varshini Rajendran
2024-07-30 16:50   ` Rob Herring
2024-07-29  7:06 ` [PATCH v6 03/27] dt-bindings: atmel-ssc: add microchip,sam9x7-ssc Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 04/27] dt-bindings: serial: atmel,at91-usart: add compatible for sam9x7 Varshini Rajendran
2024-07-29  7:06 ` [PATCH v6 05/27] dt-bindings: microchip: atmel,at91rm9200-tcb: add sam9x7 compatible Varshini Rajendran
2024-07-30 19:04   ` Rob Herring
2024-07-29  7:07 ` [PATCH v6 09/27] dt-bindings: clocks: atmel,at91sam9x5-sckc: add sam9x7 Varshini Rajendran
2024-07-29  7:07 ` [PATCH v6 10/27] dt-bindings: clocks: atmel,at91rm9200-pmc: add sam9x7 clock controller Varshini Rajendran
2024-07-29  7:08 ` [PATCH v6 14/27] dt-bindings: clock: at91: Allow PLLs to be exported and referenced in DT Varshini Rajendran
2024-07-29  7:08 ` [PATCH v6 16/27] dt-bindings: interrupt-controller: Add support for sam9x7 aic Varshini Rajendran
2024-07-29 16:24   ` Rob Herring
2024-07-29  7:09 ` [PATCH v6 21/27] dt-bindings: reset: atmel,at91sam9260-reset: add sam9x7 Varshini Rajendran
2024-07-29  7:09 ` [PATCH v6 22/27] dt-bindings: power: reset: atmel,sama5d2-shdwc: " Varshini Rajendran
2024-07-29  7:09 ` [PATCH v6 25/27] ARM: dts: at91: sam9x7: add device tree for SoC Varshini Rajendran
2024-07-31  8:30   ` Krzysztof Kozlowski
2024-08-27  9:50     ` Varshini.Rajendran
2024-08-27 12:48       ` Krzysztof Kozlowski [this message]
2024-08-28  8:25         ` Varshini.Rajendran
2024-08-28 11:49           ` Krzysztof Kozlowski
2024-09-02  6:34             ` Varshini.Rajendran
2024-07-29  7:09 ` [PATCH v6 26/27] dt-bindings: arm: add sam9x75 curiosity board Varshini Rajendran
2024-07-29  7:10 ` [PATCH v6 27/27] ARM: dts: microchip: sam9x75_curiosity: " Varshini Rajendran
2024-07-29  8:17 ` [PATCH v6 00/27] Add support for sam9x7 SoC family Andrei.Simion
2024-07-29  8:57   ` Varshini.Rajendran
2024-07-29 18:52 ` Rob Herring (Arm)
2024-08-09  6:24 ` claudiu beznea

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=5fbc815f-d52e-437d-bdc3-c61f365e9d1c@kernel.org \
    --to=krzk@kernel.org \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Varshini.Rajendran@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@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).