#asahi-dev · 2025-08-27 11:38
jannauI'll ask for a clarification#asahi-dev · 2025-08-27 11:38
jannauI missed that. That would require driver changes as we would have to add :apple,t8110-dart" to the driver to use compatible = "apple,t6020-dart", "apple,t8110-dart"; in new device trees#asahi-dev · 2025-08-27 11:33
jannaushall I ask for acked-by to take the dt-bindings patches through the asahi tree?#asahi-dev · 2025-08-27 11:31
jannaukettenis: I've seen there is power handling in marcan's outstanding patches prior to bcm4388 support#asahi-dev · 2025-08-27 11:25
jannauI plan to send it later today#asahi-dev · 2025-08-27 11:24
jannauDT t602x series is in https://github.com/jannau/linux/commits/b4/dt-apple-t6020/#asahi-dev · 2025-08-27 08:56
jannauI have the wifi node in the t602x DT submission so the compatible is used (and causes dtbs_check complaints if it's omitted from the bindings)#asahi-dev · 2025-08-27 08:47
jannauis it acceptable to add bcm4388 to brcmfmac's dt-bindings without driver support?#asahi-dev · 2025-08-27 08:41
jannauotherwise I'd say that's something https://docs.kernel.org/scheduler/sched-energy.html should consider#asahi-dev · 2025-08-27 08:34
jannauscx_nest seems match somewhat#asahi-dev · 2025-08-27 08:26
jannaumaybe there is a sched_ext scheduler which does this (or it's easy to add this via sched_ext)#asahi-dev · 2025-08-27 08:21
jannauhttps://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=sched/core&id=778c558f49a2cb3dc7b18a80ff515e82aa813627 has you covered except that does the opposite of what you want#asahi-dev · 2025-08-27 08:18
jannauI'd not be surprised if android has some out of band management for that otherwise I'd expect that's something the scheduler needs to handle#asahi-dev · 2025-08-27 08:14
jannauchaos_princess: how is the kernel to decide necessary? Are you looking into some sort of CPU idle management which tries to keep an entire cluster idle? i.e. keeps one of the perf core cluster idle on t60x0 when only 4 perf cores are used#asahi-dev · 2025-08-24 15:38
jannauthe prefix isn't necessary but I was wondering if you're using DT_SCHEMA_FILES. errors can be hard to spot with a full dt_binding_check#asahi-dev · 2025-08-24 15:30
jannauare you aware of `make dt_binding_check DT_SCHEMA_FILES=apple,atcphy.yaml`?#asahi-dev · 2025-08-24 14:35
jannauis the difference between t8103-atcphy and t6000-atcphy something which makes sense as tuneable or is it just to hide difference?#asahi-dev · 2025-08-24 14:33
jannauack on dropping the dp-only compatible#asahi-dev · 2025-08-24 14:32
jannaulooks at least nicer in so far that it get's rid of all but one if in core.c#asahi-dev · 2025-08-24 12:58
jannauusb-c still works with only "apple,t8103-dwc3" as compatible#asahi-dev · 2025-08-24 12:57
jannauI've pushed asahi-6.16.3-1 to github, usual rebase and preparation for usb3/usb-c upstreaming#asahi-dev · 2025-08-23 13:06
jannauthat probably still causes problems if dwc-of-simple is compiled in and dwc3-apple is a module#asahi-dev · 2025-08-23 13:05
jannauif we're lucky it tries to probe the device using the leftmost compatible#asahi-dev · 2025-08-23 13:04
jannauI mean we should add it now to all downstream driver (linux, openbsd, u-boot)#asahi-dev · 2025-08-23 13:01
jannauwe should start adding "apple,t8103-dwc3" in the downstream drivers#asahi-dev · 2025-08-23 12:58
jannauand I think we can't add it in m1n1 without randomly breaking setups with the glue driver#asahi-dev · 2025-08-23 11:59
jannautesting the same patch here. there's another ioremap in dwc3_get_num_ports() which is only called for host mode only designs#asahi-dev · 2025-08-23 11:51
jannauI did not look at it at all then#asahi-dev · 2025-08-23 11:28
jannauI vaguely rememeber that it moved around so it could be possible that's not needed anymore#asahi-dev · 2025-08-23 11:27
jannaugreat. does it get us dropping some core patches? I don't remember details about we need to skip host-vbus-glitches but I don't think I looked thoroughly#asahi-dev · 2025-08-23 05:23
jannauchadmed_: 64-bit integer division isn't universally available on 32-bit#asahi-dev · 2025-08-22 07:57
jannauyes, I was thinking the same. added in https://lore.kernel.org/all/20250414-dwc3-refactor-v7-0-f015b358722d@oss.qualcomm.com/ (April 2025) but started in at the end of 2023#asahi-dev · 2025-08-22 07:20
jannauiphone (pro) have so far only usb3 with dp-altmode. I wouldn't be surprised if A family SoCs lack apciec if the saved die space is worth the effort. even the ipad airs with m2/m3 do not advertise usb4#asahi-dev · 2025-08-22 06:56
jannauI think the iphone 15 pro uses the spmi variant, sn201202x. also not sure if it makes sense to worry about devices which likely will never run linux#asahi-dev · 2025-08-22 06:27
jannauI think R reversed it#asahi-dev · 2025-08-22 06:24
jannauit's third-party IP so there might be a linux driver. not upstream though (checked around 2022)#asahi-dev · 2025-08-22 06:22
jannauI don't think anyone started writing a linux driver for the jpeg block#asahi-dev · 2025-08-22 06:20
jannaunickchan: I was mustly wondering if there are devices with cd321x without thunderbolt or displayport when reading the commit description of "[PATCH RFC 14/22] usb: typec: tipd: Register DisplayPort and Thunderbolt altmodes for cd321x"#asahi-dev · 2025-08-21 20:18
jannauI think it would be fine merge after rebase. maybe replace the easy parts from the ugly struct with direct rust adt calls. we can complete it later#asahi-dev · 2025-08-21 17:22
jannaureplied to everything I noticed#asahi-dev · 2025-08-21 17:19
jannauare ps_atc1_usb_aon and ps_atc1_common the power domains from the ADT and parents of ps_atc1_usb? wondering about the commented power-domains in t8103.dtsi#asahi-dev · 2025-08-21 17:01
jannauhas any of ipads with type-c port an exploitable bootrom (i.e. ipad pro 2018)? Those probably use cd321x but don't support usb4/thunderbolt#asahi-dev · 2025-08-21 13:59
jannauno, but it'll move the complex code to deal with the mismatch to user space#asahi-dev · 2025-08-20 16:34
jannaunot used in u-boot and the use downstream kernel use is very inconsequential#asahi-dev · 2025-08-19 15:46
jannaubut I see why not when the existing compatible is still compatible#asahi-dev · 2025-08-19 15:45
jannauI would hope the minimal changes (add t6020 SoC variant compatibles to existing dt-bindings) will be accepted. if not I'd have to make also several driver changes#asahi-dev · 2025-08-19 15:22
jannauwe do not want to tons of compatibles to the drivers. for the t602x series I'll just add t6020 compatibles to the bindings and the device tree gets both. i.e. `compatible = "apple,t6020-dart", "apple,t8110-dart";`#asahi-dev · 2025-08-19 15:19
jannauI wouldn't expect per SoC differences for something low level as DART so using t8110 should be fine. t602x seems to be entirely compatible as well#asahi-dev · 2025-08-19 14:56
jannauI'd say leave the existing compatibles as is and use SoC specific ones going forward#asahi-dev · 2025-08-19 14:55
jannauapple's devicetree has up to m4 pro "role = ANS2" whatever role means