ChanServ changed the topic of #linux-msm to:
lumag_ has quit [Ping timeout: 480 seconds]
rawoul has quit [Server closed connection]
rawoul has joined #linux-msm
hexdump0815 has joined #linux-msm
hexdump01 has quit [Ping timeout: 480 seconds]
irungentoo has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
irungentoo has joined #linux-msm
u0_a259 has joined #linux-msm
<u0_a259> hello
<u0_a259> is there anybody alive?
<u0_a259> m?
u0_a259_ has joined #linux-msm
u0_a259 has quit [Ping timeout: 480 seconds]
<z3ntu> bamse: because I mentioned external pullups on I2C busses very recently, this patchset was sent and implements this https://lore.kernel.org/linux-arm-msm/20220203164629.1711958-1-vladimir.zapolskiy@linaro.org/T/ \o/
<z3ntu> > Quite regularly I2C bus lines on QCOM CCI controller require an external pull-up to a regulator powered line, to be able to define all such cases an additional vbus-supply property of a bus subnode is wanted.
pevik_ has joined #linux-msm
<z3ntu> (at least for the CCI use case which I'm most interested in right now)
lumag_ has joined #linux-msm
u0_a259 has joined #linux-msm
u0_a259_ has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
Danct12 has quit [Ping timeout: 480 seconds]
z3ntu has quit [Server closed connection]
z3ntu has joined #linux-msm
u0_a259 has quit [Quit: leaving]
<Mis012[m]> z3ntu: but it should be general to all i2c nodes...
<z3ntu> Yeah probably, not sure how easy or difficult it would be to implement generically. Or maybe it has to be implemented in like geni-i2c driver and all other drivers
norris_ has joined #linux-msm
norris has quit [Ping timeout: 480 seconds]
norris_ is now known as norris
lumag_ has quit [Ping timeout: 480 seconds]
lumag_ has joined #linux-msm
Danct12 has joined #linux-msm
<bamse> z3ntu: ahh, thanks for the link, now i finally understands what Vladimir meant...
Daanct12 has quit [Ping timeout: 480 seconds]
<bamse> Mis012[m]: there's a lot of busses that has this need...so yeah seems like a very specific solution to a generic problem, need to look around to see if we have any prior art on how to represent this
<z3ntu> To be more specific, e.g. on Fairphone 4 there's a 2.2Kohm resistor connecting CCI_I2C_SDA1 to VREG_L6P_1P8 and another resistor connecting VREG_L6P_1P8 to CCI_I2C_SCL1
<z3ntu> The same setup seems to exist for all i2c busses, connecting them to different regulators
<Mis012[m]> heh, they have you schematics?
<Mis012[m]> *gave
<z3ntu> I am schematic
<bamse> z3ntu: you said vreg_l6p in both cases, was that intentional?
<bamse> z3ntu: i.e. are you trying to say that you have two regulators, or just two different resistor values?
<z3ntu> this is what I'm trying to say :D
<bamse> that's a language i understand :)
<bamse> and that's how it pretty much always looks like...but in general vreg_l6p_1p8 is a regulator that is so critical that it won't be under software control
<z3ntu> I see exactly the same thing on msm8974 & msm8953 boards as well in the schematics
<bamse> you will find this on most i2c busses in any device
<Mis012[m]> that's nice of them... (I doubt someone would leak schematics for this nieche of a product)
<z3ntu> That I disagree with, at least on CCI busses a separate non-essential regulator seems to get used mostly
<Mis012[m]> usually all the pull-ups will use the same regulator, because I guess regulators are expensive :P
<z3ntu> e.g. on msm8974 pm8941_lvs2 is used, on the msm8953 board it's a fixed-regulator (with gpio enable) and on the sm7225 (where the screenshot is from) a pm8008 regulator gets used
<Mis012[m]> and the device already has an always-on LTE modem, so they are clearly not minmaxing power consumption :P
<z3ntu> I'm guessing the CCI pullups are a different one because they're sleeping most of the time, and to not leak power (I think that's how it works..)
<z3ntu> sensor i2c makes less sense because that ones active quite often anyways I guess
<bamse> z3ntu: isn't pm8008 the "camera pmic"?
<z3ntu> yes
<Mis012[m]> sensors are not really active when CPU sleeps... though that's not quite true with sensor hubs
<bamse> regardless, the problem is there and need to be resolved
<z3ntu> yep :)
<z3ntu> on CCI bus not even i2cdetect works if the pullup isn't active; you also get verbose errors in dmesg when that happens
<bamse> z3ntu: and yes you're right...there's some leaks related to just keeping the regulator on etc, so if some part of the device can be fully powered down 99% of the time that's nice
<bamse> z3ntu: that's expected, based on how i2c works
<bamse> z3ntu: i.e. idling high and the communication happens by pulling the lines down
<z3ntu> ¯\_(ツ)_/¯ haha
<minecrell> z3ntu: I think these regulators are typically managed by the device in Linux and not the bus, but it's not always accurate
<minecrell> e.g. for i2c touchscreens and sensors there is typically some kind of vddio-supply or so. Which in some cases is actually just the pull up for i2c, but in other cases it can also be an actual input of the chip. This is quite inconsistent...
<z3ntu> And imo when it's known that some regulator is providing pullup then it makes sense to model it that way in dt. Of course for some random device when it just magically works and you don't have schematics then you cannot add it
<Mis012[m]> you could try to find pull-ups with a multimeter :P
travmurav[m] has joined #linux-msm
<RayyanAnsari[m]> <z3ntu> "e.g. on msm8974 pm8941_lvs2 is..." <- on msm8226 lvs1 is used
<z3ntu> probably different per board
<RayyanAnsari[m]> for now i used `regulator-always-on`
<z3ntu> or maybe it's from the reference design
<RayyanAnsari[m]> dunno if there's a proper way
<RayyanAnsari[m]> <z3ntu> "bamse: because I mentioned..." <- with these patches i could use `vbus-supply = <&pm8226_lvs1>`
<RayyanAnsari[m]> s/>`/>`?/
<z3ntu> that's the idea
<Guest337> ah okay
<Guest337> whoops
Guest337 is now known as Rayyan
<Rayyan> there
<Mis012[m]> vbus is the name of a USB connector pin... not sure that's the best name
ehsbg has joined #linux-msm
<ehsbg> @`.D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a t o
<ehsbg> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ehsbg> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ehsbg>
<ehsbg> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ehsbg>
<ehsbg> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s
ehsbg has quit [Remote host closed the connection]
eiorghg has joined #linux-msm
eiorghg has quit [Excess Flood]
<Rayyan> will these spammers ever go away
ejgtsh has joined #linux-msm
<Mis012[m]> could set up a spam filter :P
<ejgtsh> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ejgtsh>
<ejgtsh> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ejgtsh> @`..D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a t o
<ejgtsh> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ejgtsh> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s@`..D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a
<ejgtsh>
<ejgtsh> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ejgtsh> t o
<ejgtsh>
<ejgtsh> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ejgtsh> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ejgtsh>
<ejgtsh> t o
<ejgtsh> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s@`..D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a
<ejgtsh> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ejgtsh> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ejgtsh> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ejgtsh>
<ejgtsh>
<ejgtsh> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s@`..D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a
<ejgtsh> t o
<ejgtsh> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ejgtsh> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ejgtsh>
<ejgtsh>
<ejgtsh> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ejgtsh> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s@`..D\..@`I.\.@`.\D` U>@\`S`@\>`@\A . t`^@\ R\@` a`@ \i` n & s u@` \p. p@\. l y i `\.s< .@\`i`\ s w i t h .W e\< `\a <\P` \ o n s l i k e i t d i d w i \ t h a .l< Q@ .a \ @\ \e \d \a
<ejgtsh> t o
<ejgtsh> J u/ s. .t <i f y c r .ea \ t.\ i n g w < \a \ r\ .s
<ejgtsh> a m \.e r .<i c \a n s n e \e d .e d s o m e .\t h i n g. L i .\ k e . 9 . \ \. 11 t o J u/ s. .t <i f y i n >/.v .A . d .i n g - .i `r@ .a \
<ejgtsh>
<ejgtsh> d \i. d C\< @ `I\@\`a - d< \i .d . 911 o r i t j u s t l .e\ t i t h a p. p e n
<ejgtsh>
<ejgtsh> i\ f a .l< Q@ .a \ @\ \e \d \a d. i\ d i t W \ H \ Yt o k -\i .<l -\l 9 m i \L. \l \i \o \n .i `r@ .a \q@\i \s
ejgtsh has quit [Remote host closed the connection]
<Rayyan> lol
<Mis012[m]> I'm amazed that it's worth it to someone to use their botnet to spam 9/11 conspiracy stuff on irc
<Mis012[m]> and they add special characters because what? do they think someone has an automatic spam filter that doesn't get triggered by that, but gets triggered by 9/11 related keywords?
<mal> also strange to spam in a way that is almost unreadable, other than to prevent being caught by filters, but being unreadable makes it quite pointless, although spamming in irc is quite pointless anyway
<Rayyan> i remember it used to be normal
<Rayyan> over time they started inserted characters in between letters
<Rayyan> dunno why they do it in the first place
<Rayyan> but oftc needs to sort it out
<mal> yes, in the past there was quite much spamming
<Mis012[m]> it must be trivial to come up with a 0% false positive heuristic
<Mis012[m]> it looks nothing like a regular message
<minecrell> bamse: Btw, you seem to have accidentally used "qcom,sm8350-slpi-pas" rather than sm8450 in https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=e57f31b02784bdafd35940ea2592df8151ea1190
pevik_ has quit [Ping timeout: 480 seconds]
<bamse> minecrell: thanks for spotting that, thought i had fixed them...mind sending a patch?
<minecrell> bamse: I will probably forget since I have too many things going on in parallel atm, but maybe someone else here is looking for an easy patch to submit :)
<bamse> minecrell: fair enough...i'm just worried that if i post it and wait for a review it will sit on the list for a while...or ever...
<bamse> minecrell: but now i'm aware and it will bother me
<minecrell> bamse: it definitely needs a thorough review :p
<bamse> well, i spelled 8450 wrong once ;)
<Mis012[m]> bamse: it's not even -next, can't you just squash it?
<bamse> Mis012[m]: if it's only a few hours old and not part of linux-next i can do that...
<bamse> Mis012[m]: it's been a long week...forgot that i did that earlier today
<bamse> minecrell: there...it never happened
<bamse> minecrell: thanks :)
<minecrell> bamse: you need to push for-next too
<bamse> minecrell: i did...maybe need to refresh?
<minecrell> weird, https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git shows arm64-for-5.18 but not for-next
<bamse> https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/log/?h=for-next says that i merged the dts change 4 minutes ago
<minecrell> it doesn't for me
<minecrell> Some CDN is caching things I guess :D
<Mis012[m]> and I definitely wasn't on that page lately
<Mis012[m]> fun
<minecrell> now it's right
<Mis012[m]> indeed
prawn has joined #linux-msm