could be worth making duty cycle an optional extra arg when setting clock freq

[mattvenn]

https://github.com/TinyTapeout/tt-commander-app/blob/9e7b705562b5a66526e8e959f2870b6348983235/src/ttcontrol/ttcontrol.py#L106

[urish]

Is there an actual use case or just "nice to have"?

Duty cycle is pretty tricky, since the actual duty cycle you can achieve depends on the frequency (e.g. at 50 MHz, you can only achieve 50% duty cycle). So if this is not a common use case, I think it's better not to support this in the commander.

[mattvenn]

It came up in the Z2A discord recently. I doubt it will be a common use case, so if it's not trivial to add, then happy to close this.

On Sun, 12 May 2024 at 16:59, Uri Shaked @.***> wrote:

Is there an actual use case or just "nice to have"?

Duty cycle is pretty tricky, since the actual duty cycle you can achieve depends on the frequency (e.g. at 50 MHz, you can only achieve 50% duty cycle). So if this is not a common use case, I think it's better not to support this in the commander.

— Reply to this email directly, view it on GitHub https://github.com/TinyTapeout/tt-commander-app/issues/12#issuecomment-2106274268, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE223B6JBHCAHUJ54FEV4DZB57TVAVCNFSM6AAAAABHS3D3UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGI3TIMRWHA . You are receiving this because you authored the thread.Message ID: @.***>

-- Matthew Venn web mattvenn.net twitter @matthewvenn https://twitter.com/matthewvenn