diff options
| author | Mark Brown <[email protected]> | 2024-04-17 09:12:19 +0900 |
|---|---|---|
| committer | Mark Brown <[email protected]> | 2024-04-17 09:12:19 +0900 |
| commit | 1f05252a3a95bb898413126d3cd480fed4edab0e (patch) | |
| tree | d19f29a1fed2c3168053e5410304f4b0c191f964 /kernel/time/tick-sched.h | |
| parent | 351007b069287d3f0399e9e83981b33a2050eb54 (diff) | |
| parent | 439fbc97502ae16f3e54e05d266d103674cc4f06 (diff) | |
Add bridged amplifiers to cs42l43
Merge series from Charles Keepax <[email protected]>:
In some cs42l43 systems a couple of cs35l56 amplifiers are attached
to the cs42l43's SPI and I2S. On Windows the cs42l43 is controlled
by a SDCA class driver and these two amplifiers are controlled by
firmware running on the cs42l43. However, under Linux the decision
was made to interact with the cs42l43 directly, affording the user
greater control over the audio system. However, this has resulted
in an issue where these two bridged cs35l56 amplifiers are not
populated in ACPI and must be added manually. There is at least an
SDCA extension unit DT entry we can key off.
The process of adding this is handled using a software node, firstly the
ability to add native chip selects to software nodes must be added.
Secondly, an additional flag for naming the SPI devices is added this
allows the machine driver to key to the correct amplifier. Then finally,
the cs42l43 SPI driver adds the two amplifiers directly onto its SPI
bus.
An additional series will follow soon to add the audio machine driver
parts (in the sof-sdw driver), however that is fairly orthogonal to
this part of the process, getting the actual amplifiers registered.
Diffstat (limited to 'kernel/time/tick-sched.h')
| -rw-r--r-- | kernel/time/tick-sched.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/time/tick-sched.h b/kernel/time/tick-sched.h index e11c4dc65bcb..b4a7822f495d 100644 --- a/kernel/time/tick-sched.h +++ b/kernel/time/tick-sched.h @@ -46,8 +46,8 @@ struct tick_device { * @next_tick: Next tick to be fired when in dynticks mode. * @idle_jiffies: jiffies at the entry to idle for idle time accounting * @idle_waketime: Time when the idle was interrupted + * @idle_sleeptime_seq: sequence counter for data consistency * @idle_entrytime: Time when the idle call was entered - * @nohz_mode: Mode - one state of tick_nohz_mode * @last_jiffies: Base jiffies snapshot when next event was last computed * @timer_expires_base: Base time clock monotonic for @timer_expires * @timer_expires: Anticipated timer expiration time (in case sched tick is stopped) |