From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ben Zong-You Xie <ben717@andestech.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: add atcpit100-pwm
Date: Mon, 28 Oct 2024 15:42:09 +0100 [thread overview]
Message-ID: <617a641b-d567-4580-8c8c-db489051026b@kernel.org> (raw)
In-Reply-To: <20241028102721.1961289-2-ben717@andestech.com>
On 28/10/2024 11:27, Ben Zong-You Xie wrote:
> +---
> +$id: http://devicetree.org/schemas/pwm/andestech,atcpit100-pwm.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: PWM driver for Andes atcpit100
Driver as Linux driver?
> +
> +maintainers:
> + - Ben Zong-You Xie <ben717@andestech.com>
> +
> +allOf:
> + - $ref: pwm.yaml#
> +
> +properties:
> + compatible:
> + const: andestech,atcpit100-pwm
> +
> + reg:
> + maxItems: 1
> +
> + "#pwm-cells":
> + const: 2
> +
> + andestech,clock-source:
> + description:
> + Clock Source for each PIT channel.
> + 0 - external clock
> + 1 - APB clock.
You don't take APB clock here... neither external. Where is the clocks
property?
Why assigned-clocks cannot work here?
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + minItems: 4
> + maxItems: 4
> + items:
> + minimum: 0
> + maximum: 1
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-28 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 10:27 [PATCH 0/2] pwm: add PWM driver for atcpit100 Ben Zong-You Xie
2024-10-28 10:27 ` [PATCH 1/2] dt-bindings: pwm: add atcpit100-pwm Ben Zong-You Xie
2024-10-28 13:08 ` Uwe Kleine-König
2024-10-28 14:42 ` Krzysztof Kozlowski [this message]
2024-10-28 10:27 ` [PATCH 2/2] pwm: atcpit100: add Andes PWM driver support Ben Zong-You Xie
2024-10-28 13:38 ` Uwe Kleine-König
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=617a641b-d567-4580-8c8c-db489051026b@kernel.org \
--to=krzk@kernel.org \
--cc=ben717@andestech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ukleinek@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