Repository navigation
Conversation
… fallback The firmware asks the AP for the PMU temperature property at boot (callback D401 "PMUS"/"Temperature") for its panel compensation's initial guess; the driver answered it only for mini-LED panels, so the OLED K116s logged "set_PMU_service: failed to read PMU temperature property!" twice. Answer with the battery temperature as the H17P and v14.7 paths do. The DCP also reads eleven SMC temperature keys itself for its 2D virtual temperature model and logs once a second that TAOC is -127.0, the SMC's no-sample value, and that it uses the 2DVT fallback. TAOC and its siblings are AOP-sourced sensors the SMC has no sample for until the AOP's sensor servers run, so route that record to the debug level; another sensor, value or verdict stays at info. Signed-off-by: Jens Axboe <axboe@kernel.dk>
The filter that demotes known-benign firmware syslog records was only in the external H17P RTKit ops, so the TAOC fallback record still logged once a second on the internal panel. Signed-off-by: Jens Axboe <axboe@kernel.dk>
The 27.2 firmware sends a 20-byte D590 notification with no reply after swaps (the macOS handler next to swap_info is the buffer-release notification). Nothing here consumes it, so take it as a no-op instead of warning about an unknown callback. Signed-off-by: Jens Axboe <axboe@kernel.dk>
sithglan
force-pushed
the
thomas/k116s-dcp
branch
from
November 12, 2026 14:30
81d1f3d to
d30426f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Base: integration/aurora (050f6a5). Three commits, all in drm/apple. None of them changes behaviour, only what reaches the log:
Not included: Jens's "drm/apple: drive firmware 27.2 with the 27.0 interface and its new method numbers". Its 27.2 tags are exactly the ones in the 27.2 table of the open #1174 (Jeff's table from #894, choosing the table by
apple,firmware-compat). Jens's K116s confirms that table on hardware: AppleDCP-1317.40.16 with the +50 IOMobileFramebufferAP numbering, A389 to A390, and unchanged callbacks.Tested by Jens on the K116s (27.2, 26B8125), internal OLED panel through DCP.
Build: arm64, LLVM 22;
drivers/gpu/drm/apple/, no warnings.Authorship. Jens Axboe wrote these commits and runs them on his K116s (16-inch MacBook Pro, M5 Pro, OLED; Mac17,12; stub macOS 27.2 26B8125). They come from his K116s bundle of 2026-11-11 (integration/aurora 254c9bd plus 34 commits, kernel 7.3.0 running on the machine). I rebased them onto integration/aurora 050f6a5 and removed the LLM co-author and session trailers. Jens has given his OK: the commits carry his Signed-off-by.