add disable gyro clock

[cvetaevvitaliy]

add disable gyro clock for testing and comparing results ICM42688P

Usage

• add -DUSE_DISABLE_GYRO_CLKIN using EXTRA_FLAGS for local build
• add DISABLE_GYRO_CLKIN using custom define for cloud build

[ot0tot]

Why not just disable the resource in the CLI?

[cvetaevvitaliy]

It is much more convenient to disable before build сб, 3 трав. 2025 р. о 23:20 ot0tot ***@***.***> пише:

…

*ot0tot* left a comment (betaflight/config#767) <#767 (comment)> Why not just disable the resource in the CLI? — Reply to this email directly, view it on GitHub <#767 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJSSOHAMPGQM7PGYTMV3FD24UQHPAVCNFSM6AAAAAB4LS6FEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBYG44TANRRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[SteveCEvans]

Why not just disable the resource in the CLI?

Exactly my thought. That’s easy and obvious, whereas build options are not so easily remembered and have a habit of becoming broken over time when the code is updated and their significance is overlooked.

[cvetaevvitaliy]

Why not just disable the resource in the CLI?

Exactly my thought. That’s easy and obvious, whereas build options are not so easily remembered and have a habit of becoming broken over time when the code is updated and their significance is overlooked.

Only non-developer wouldn't do this. Finally it's only for one target and as part of testing this feature for a quick comparison - Enable/Disable gyro clock

[ot0tot]

If only for testing it makes even more sense to just do it in the CLI. No need to recompile the firmware and reflash.

[SteveCEvans]

Exactly. Once tested and proven it would be dead, unused complexity.

[haslinghuis]

Closing as developers can just disable the pin (no need for new local define)