public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Farouk Bouabid <farouk.bouabid@cherry.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	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 2/6] pwm: add mule pwm-over-i2c driver
Date: Wed, 17 Jul 2024 10:48:52 +0200	[thread overview]
Message-ID: <33d93798-459b-4d33-ac59-623a68ea48cf@cherry.de> (raw)
In-Reply-To: <e7b3bfpvtrvt5g637yy7qxsbvfiylyzrjvwsro4hzp5t6cmeux@eqafx3k7oaks>

Hi Uwe,

On 7/15/24 5:09 PM, Uwe Kleine-König wrote:
> Hello Quentin,
> 
> On Mon, Jul 15, 2024 at 02:16:15PM +0200, Quentin Schulz wrote:

[...]

>> To give a bit more info on this, there are two possible flavors of the MCU,
>> ATtiny 816 (datasheet: https://ww1.microchip.com/downloads/en/DeviceDoc/ATtiny416-816-DataSheet-DS40001913B.pdf)
>> and STM32F072CB (datasheet: https://www.st.com/content/ccc/resource/technical/document/reference_manual/c2/f8/8a/f2/18/e6/43/96/DM00031936.pdf/files/DM00031936.pdf/jcr:content/translations/en.DM00031936.pdf).
>>
>> FYI, on ATtiny, we use TCA in single-slope PWM generation mode and PERBUF
>> and CMP2BUF as period and duty-cycle registers. On STM32, we use TIM15 in
>> PWM mode and ARR and CCR1 as period and duty-cycle registers.
> 
> Wouldn't it be more natural with these to have duty in a base-2 register
> for duty, in the assumption that your MCUs habe this, too?
> 

Not sure to understand what you meant by base-2 register here? I am 
guessing you rather wanted to suggest a different unit/representation of 
the duty cycle in the register in the FW API?

Cheers,
Quentin


  reply	other threads:[~2024-07-17  8:50 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
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 [this message]
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=33d93798-459b-4d33-ac59-623a68ea48cf@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=farouk.bouabid@cherry.de \
    --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=robh@kernel.org \
    --cc=u.kleine-koenig@baylibre.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