19:04 <aka_[m]> I do want to try port some funky device and it turns out it has some gpio stuff for antena.

19:04 <aka_[m]> Together with Toonis we came to idea putting default pin states for modem and wcnss remoteproc will it work or two devices cannot share same pinctrl state?

19:04 <aka_[m]> Xiaomi decided to write its own driver to just set pinctrl state.

19:05 <aka_[m]> or try to model it as fixed regulator which is always on?

19:06 <aka_[m]> in case of modem im not sure if putting remoteproc state to sleep will kick RF part out.

19:28 <Mis012[m]> aka_: according to the schematic, it's an output

19:28 <Mis012[m]> eh

19:28 <Mis012[m]> not

19:28 <Mis012[m]> an input to the SoC

19:29 <Mis012[m]> and it would make more sense than the alternative considering how it's connected

19:29 <Mis012[m]> the nice thing about inputs is that you can probably just ignore them :P

19:30 <aka_[m]> some ppl say its not enabled by default

19:31 <aka_[m]> it is

19:31 <aka_[m]> ehh

19:32 <Mis012[m]> I doubt you need to "enable" anything

19:32 <Mis012[m]> if it's an input pin

19:32 <Mis012[m]> and it doesn't seem to need any internal pull-up/down

19:33 <Mis012[m]> well, I don't think Linux userspace has a need for information on the state of some antenna?

19:33 <Mis012[m]> `drivers/bus/qcom-ssc-block-bus.c:217:17: error: assigning to 'const char **' from 'const char *const[2]' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]`

19:33 <Mis012[m]> uh hm

19:34 <Mis012[m]> I swear gcc didn't complain

19:34 <Mis012[m]> I wonder if that's why they use clang for the bot...

19:35 <Mis012[m]> to catch you on stuff your local gcc which you're clearly using didn't report

19:37 <Mis012[m]> aka_: if you get someone with RF knowledge to look at it, maybe you can make a `gpio-antenna-status` binding :P

19:38 <aka_[m]> maybe i will try with fake fixed-regulator tho

19:38 <Mis012[m]> ???

19:38 <Mis012[m]> that's for output

19:38 <Mis012[m]> this is input

19:38 <aka_[m]> not sure how RF1/RF2/RF3 works

19:39 <aka_[m]> uh

19:39 <Mis012[m]> pretty sure they got the direction right in the schematic

19:40 <aka_[m]> so how we set input vs output in pinctrl?

19:40 <aka_[m]> https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commit/7c412528d67834237d87505b9e1479df46a440c5#diff-7bc12e4b0e377eafdc8dab7d10b7eff7d6a69d3b0b5f96f8504015460ac07f8dR1598

19:41 <Mis012[m]> this looks to me like the 470K resistor is pulling it up

19:42 <Mis012[m]> and when that top line gets pulled LOW, it will pull the signal low through the 10K resistor

19:42 <Mis012[m]> so basically it's an input that tells you if that top line is LOW

19:42 <Mis012[m]> and presumably it usually won't be

19:43 <Mis012[m]> since you would prefer to have the 470K resistor loading your battery all the time rather than the 10K one

19:44 <Mis012[m]> https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commit/7c412528d67834237d87505b9e1479df46a440c5#diff-7bc12e4b0e377eafdc8dab7d10b7eff7d6a69d3b0b5f96f8504015460ac07f8dR1607

19:44 <Mis012[m]> you will want this

19:45 <Mis012[m]> https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml#L73

19:45 <Mis012[m]> this is what you're looking for