devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Keerthy <j-keerthy@ti.com>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] dt-bindings: timer: Update TI timer to yaml and add compatible for am6
Date: Fri, 8 Apr 2022 13:07:42 +0300	[thread overview]
Message-ID: <YlAJbgqpHLEfYIjO@atomide.com> (raw)
In-Reply-To: <d8ad6a2b-0982-a7f2-c331-cced4e321c7c@linaro.org>

* Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> [220408 08:30]:
> On 08/04/2022 10:12, Tony Lindgren wrote:
> > +required:
> > +  - compatible
> > +  - reg
> 
> Missing interrupts - they were required. Aren't anymore?

There are cases where the interrupts are not routable to Linux yet
the timer registers can be accessible. These timers can still be usable
in a limited way for some PWM cases though.

Thanks for the good comments on the binding, will update accordingly.
Yeah adding a second patch for the new features makes sense as few
things have changed with the new SoCs.

Regards,

Tony

  reply	other threads:[~2022-04-08 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  8:12 [PATCH] dt-bindings: timer: Update TI timer to yaml and add compatible for am6 Tony Lindgren
2022-04-08  8:27 ` Nishanth Menon
2022-04-08  8:33   ` Tony Lindgren
2022-04-08  8:34   ` Krzysztof Kozlowski
2022-04-08  8:32 ` Krzysztof Kozlowski
2022-04-08 10:07   ` Tony Lindgren [this message]
2022-04-08 15:41 ` Rob Herring
2022-04-11  8:00   ` Tony Lindgren

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=YlAJbgqpHLEfYIjO@atomide.com \
    --to=tony@atomide.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).