00:03 <konradybcio> hopefully not another housewarmer :)

00:39 <vknecht[m]> what's its real name ? 8gen1 seems to be sm8450 and 8+gen1 == sm8475 are the latest according to wikipedia list of qcom SoCs

00:40 <vknecht[m]> other than that, commercial hype feels depressing, like, it was the same kind of press releases 8 years ago (and more) and where are those products, how are they supported now ?

00:46 <vknecht[m]> so... trm, hrd, docs, schematics, or it didn't happen :-)

00:50 <vknecht[m]> (right msm8916 is the exception)

01:03 <ndec> vknecht[m]: it's next gen soc, so name is sm8550

08:46 <z3ntu> sm8450 is already a year old? wow..

08:46 <z3ntu> So then are the sm8550 patches flying in? ;)

08:46 <z3ntu> *when

09:36 <Tooniis[m]> <ndec> "exiting day, https://www...." <- https://www.qualcomm.com/products/application/smartphones/snapdragon-8-series-mobile-platforms/snapdragon-8-gen-2-mobile-platform

09:36 <Tooniis[m]> > Qualcomm Sensing Hub: Dual-core AI processor, Always-sensing camera

09:36 <Tooniis[m]> cameras behind ssc now?

09:37 <Tooniis[m]> and "always-sensing"?

09:38 <Tooniis[m]> camera stickers will become an actually decent idea

09:51 <Marijn[m]> <z3ntu> "So then are the sm8550 patches..." <- https://lore.kernel.org/linux-arm-msm/2ce5bc21-c4c5-ed61-3683-3288ed1057e2@linaro.org/ 👀

11:09 <aka_[m]> Msm-5.15 comming quite soon

11:09 <aka_[m]> Then

11:41 <z3ntu> Ah here are the SM8550 patches (finally!): https://lore.kernel.org/linux-arm-msm/20221116103146.2556846-1-abel.vesa@linaro.org/T/

11:42 <z3ntu> Glad to see (at least) high-end SoCs be supported so quickly :)

11:42 <z3ntu> Now the same is just missing for all the lower-end ones also haha ;)

11:52 <konradybcio> linaro has been upstreaming 8 series on day1 for a few gens now

12:13 <z3ntu> Personally haven't noticed before 8450 but I also haven't been really monitoring linux-arm-msm list before then

12:30 <Tooniis[m]> how many pmics does this thing need

13:08 <ajhalaney[m]> :D I thought the same thing

15:47 <lumag> konradybcio, regarding smmu. I don't have a clear picture of -smmu-v2 entries. If I remember correctly some of them are more broken ('secured') than others are.

15:47 <konradybcio> yes, that's the case

15:47 <konradybcio> 630 vs 8996/8 vs 845 (vs i want to add 6350)

15:47 <lumag> For qcom-smmu-500 the picture is more clear, all of them appear to be the same

15:48 <lumag> So, I'd say, we have to live with per-SoC entries for -v2 entries, while all qcom 500 entries can be handled by the generic compat.

15:48 <lumag> Unless the platform has some peculiarities (e.g. sdm845)

15:48 <konradybcio> okay, sounds good

18:01 <aka_[m]> konradybcio: any idea if latest rc work now?

18:01 <aka_[m]> or next

18:11 <konradybcio> idk i have next 20221115 and Brian's patch picked into my tree

18:18 <aka_[m]> i should rebase dpu patches and compile test them

18:18 <aka_[m]> but tree was quite broken

18:34 <aka_[m]> so "day one" support mean 5.15 msm fork will come within days?

18:34 <aka_[m]> yes we are here about mainline, but i seen some notes about qcom doing 5.15 ds quite fancy

18:34 <aka_[m]> including support for Khaje

18:50 <konradybcio> last time xiaomi released 5.10 faster than caf iirc

19:42 <aka_[m]> Flagships Inc

19:42 <aka_[m]> Right

19:42 <aka_[m]> Shouldn't qcom release caf trees day one

19:50 <konradybcio> well gpl requires they do once you receive the compiled copy