From: Farouk Bouabid <farouk.bouabid@cherry.de>
To: Conor Dooley <conor@kernel.org>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
"Heiko Stuebner" <heiko@sntech.de>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/6] dt-bindings: pwm: add dt-bindings for mule pwm-over-i2c controller
Date: Fri, 31 May 2024 18:19:23 +0200 [thread overview]
Message-ID: <0b8e06a6-9b92-495f-999d-9dfc50d17b7f@cherry.de> (raw)
In-Reply-To: <20240529-capably-overgrown-755bb11ece69@spud>
Hi Conor,
On 29.05.24 22:29, Conor Dooley wrote:
> On Wed, May 29, 2024 at 12:10:30PM +0200, Farouk Bouabid wrote:
...
>> + A device that outputs a PWM signal based on I2C commands.
>> +
>> +maintainers:
>> + - Farouk Bouabid <farouk.bouabid@cherry.de>
>> + - Quentin Schulz <quentin.schulz@cherry.de>
>> +
>> +allOf:
>> + - $ref: pwm.yaml#
>> +
>> +properties:
>> + compatible:
>> + const: tsd,pwm-mule
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + "#pwm-cells":
>> + const: 2
> No clocks or supplies?
> I tried to google for some documentation for this device, but only found
> archives of this mail thread..
You can't find documentation for this device because we don't sell it
standalone. It is part of our boards.
This device handles its clock internally. So there is no need for clock.
As for the power-supply, it is so far
always enabled but I will add a property.
Cheers,
Farouk
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-31 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 10:10 [PATCH 0/6] Add Mule PWM-over-I2C support Farouk Bouabid
2024-05-29 10:10 ` [PATCH 1/6] dt-bindings: pwm: add dt-bindings for mule pwm-over-i2c controller Farouk Bouabid
2024-05-29 20:29 ` Conor Dooley
2024-05-31 16:19 ` Farouk Bouabid [this message]
2024-05-29 10:10 ` [PATCH 2/6] pwm: add mule pwm-over-i2c driver Farouk Bouabid
2024-07-12 8:54 ` Uwe Kleine-König
2024-07-15 12:16 ` Quentin Schulz
2024-07-15 15:09 ` Uwe Kleine-König
2024-07-17 8:48 ` Quentin Schulz
2024-07-18 11:50 ` Uwe Kleine-König
2024-05-29 10:10 ` [PATCH 3/6] arm64: dts: rockchip: add pwm-beeper to rk3399-puma-haikou Farouk Bouabid
2024-05-29 10:10 ` [PATCH 4/6] arm64: dts: rockchip: add pwm-beeper to px30-ringneck-haikou Farouk Bouabid
2024-05-29 10:10 ` [PATCH 5/6] arm64: dts: rockchip: add pwm-beeper to rk3588-tiger-haikou Farouk Bouabid
2024-05-29 10:10 ` [PATCH 6/6] arm64: dts: rockchip: add pwm-beeper to rk3588-jaguar Farouk Bouabid
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=0b8e06a6-9b92-495f-999d-9dfc50d17b7f@cherry.de \
--to=farouk.bouabid@cherry.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--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