ChanServ changed the topic of #linux-msm to:
niej_ has joined #linux-msm
hexdump02 has joined #linux-msm
hexdump0815 has quit [Ping timeout: 480 seconds]
<bamse> kathirav: wouldn't that affect the other targets of that yaml as well?
<bamse> kathirav: please send the necessary patch(es) to move us in the right direction...if that's a revert, than send that and provide an explanation
flto_ has joined #linux-msm
flto has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
pespin has joined #linux-msm
jhovold has joined #linux-msm
animist has quit [Ping timeout: 480 seconds]
animist has joined #linux-msm
<kathirav> Thanks bamse, Again IIUC, we should start using mmio-sram going forward and not disturb anything which are already described in the yaml (https://lore.kernel.org/all/00f6d696-a8d2-41a5-819a-dc1ed87d35bb@kernel.org/). Since the driver changes which uses the IPQ5424's IMEM is not yet merged, so I would like to revert the binding change and use the
<kathirav> mmio-sram. Yeah, let me send out the patches in sometime.
niej_ has quit [Ping timeout: 480 seconds]
jhovold has quit [Quit: WeeChat 4.5.2]
<z3ntu> Looks like the resin (volume down) driver likes to wake up the device from suspend when pressing the button. For pwrkey obviously wanted but volume down not so much. Does this need to be adjusted in dts or driver? (Or user space?)
<sgerhold> z3ntu: The device_init_wakeup(&pdev->dev, **1**); in pm8941-pwrkey.c sets the default, it can be changed from userspace. It doesn't make much sense to have it enabled by default for resin, but changing it now might be tricky
<sgerhold> ideally the driver would look for "wakeup-source" in the DT ...
<z3ntu> sgerhold you think it's a good idea to send a patch for that and see what people say?
<z3ntu> Imo on at least 99% of phones this is not expected behavior
<z3ntu> For devboards, maybe? On laptops (do they wire up resin?) probably also not?
<z3ntu> But then maaaaybe pwrkey should have the same behavior but there it's definitely breaking to not have this by default
<z3ntu> Like reverse questions, is it a use case for some boards to disable wakeup-source on pwrkey?
<bamse> z3ntu: yes, sending a patch and making a case for resin to be default non-wake makes sense...it would "break" existing users...but that's just something we'd have to take into consideration
<bamse> z3ntu: at least if we have a patch we can argue somewhere and we have documentation of the outcome
<bamse> the crd is using resin for a volume down button...but i don't think that was inherited in any of the designs
flto_ has quit []
flto has joined #linux-msm
<z3ntu> Afaik most phones are using resin for vol-down, so that's from mtp/idp I guess
<z3ntu> bamse but ok, I'll try and make a patch tomorrow
<bamse> z3ntu: right, and i'd argue that if there actually are real users of such devices...they would agree with your view on this
<bamse> z3ntu: i'm not sure what use cases there are for disabling wakeup on power key though...
<z3ntu> Yes, for pwrkey that was my point as well, but since it's the same driver and I'll only have this behavior for resin, it's important to distinguish
pespin has quit []
sgerhold has quit [Quit: Ping timeout (120 seconds)]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #linux-msm
sgerhold has joined #linux-msm
konradybcio has joined #linux-msm
<konradybcio> i use resin wakeup as a feature.. needs no edits to systemd configs to prevent it from also shutting down the system unlike the power button
<konradybcio> but i suppose i can accept the added required 1 LoDTS on my end