IRC log of #maemo-ssu for Sunday, 2013-10-06

*** Martix_ has joined #maemo-ssu00:07
*** int_ua has quit IRC00:18
*** Martix_ has quit IRC00:18
*** nox- has joined #maemo-ssu01:01
*** kolp_ has quit IRC01:20
*** NIN101 has quit IRC01:47
*** jonwil has joined #maemo-ssu02:52
*** M4rtinK has quit IRC03:02
*** nox- has quit IRC03:38
*** dos1 has quit IRC04:20
*** dos1 has joined #maemo-ssu04:25
*** dos11 has joined #maemo-ssu04:27
*** dos1 has quit IRC04:27
*** LaoLang_cool has joined #maemo-ssu04:28
*** dos11 has quit IRC04:33
*** dos11 has joined #maemo-ssu04:41
*** dos11 has quit IRC04:45
*** LaoLang_cool has quit IRC05:06
*** MetalGearSolid has quit IRC05:13
*** MetalGearSolid has joined #maemo-ssu05:13
*** LaoLang_cool has joined #maemo-ssu05:25
*** amiconn has quit IRC05:46
*** amiconn_ has joined #maemo-ssu05:46
*** amiconn_ is now known as amiconn05:46
*** LaoLang_cool has quit IRC05:47
*** Pali has joined #maemo-ssu10:16
*** discopig has quit IRC10:18
*** DrCode has joined #maemo-ssu10:24
Palifreemangordon: any news why rtcom-call-ui crashing?10:34
Palimaybe it can be that gpio switch which is already used by snd driver?10:35
*** DrCode has quit IRC10:40
*** DrCode has joined #maemo-ssu10:51
*** discopig has joined #maemo-ssu11:01
*** Martix_ has joined #maemo-ssu11:06
*** discopig has quit IRC11:08
*** discopig has joined #maemo-ssu11:20
*** discopig has quit IRC11:24
*** discopig has joined #maemo-ssu11:29
*** Martix_ has quit IRC11:32
freemangordonPali: didn't have time to debug it11:57
freemangordonbut there are more sound switches related errors11:58
freemangordonJan  1 08:02:30 Nokia-N900 pulseaudio[1547]: voice-sidetone.c: Cannot open /sys/devices/platform/omap-mcbsp.2/st_enable12:00
freemangordonJan  1 08:02:30 Nokia-N900 pulseaudio[1547]: module-alsa-sink-volume.c: hw:0: Bad mixer mode entry Headphone:off12:00
freemangordonJan  1 08:02:30 Nokia-N900 pulseaudio[1547]: module-alsa-sink-volume.c: hw:0: Bad mixer mode entry Earphone:off12:00
freemangordonPali: ^^^12:01
*** Vlad_on_the_road has joined #maemo-ssu12:09
*** NIN101 has joined #maemo-ssu12:23
*** Martix_ has joined #maemo-ssu12:35
*** Vlad_on_the_road has quit IRC12:39
*** Vlad_on_the_road has joined #maemo-ssu12:40
*** Vlad_on_the_road has quit IRC12:47
*** M4rtinK has joined #maemo-ssu12:50
*** Vlad_on_the_road has joined #maemo-ssu13:00
*** Vlad_on_the_road has quit IRC13:16
*** Vlad_on_the_road has joined #maemo-ssu13:17
*** kolp has joined #maemo-ssu13:19
*** delphi is now known as trx13:30
*** Martix_ has quit IRC13:53
*** int_ua has joined #maemo-ssu14:10
*** dos11 has joined #maemo-ssu14:15
*** Martix_ has joined #maemo-ssu14:48
*** Vlad_on_the_road has quit IRC14:51
*** Vlad_on_the_road has joined #maemo-ssu15:05
*** int_ua has quit IRC15:19
*** Martix_ has quit IRC16:04
*** dos11 has quit IRC16:36
*** Pali has quit IRC16:47
*** Martix_ has joined #maemo-ssu16:51
FatPhilwould any of you hackers have any use for a proto with a broken USB, a slightly duff screen (not actually missing any pixels though), and a finnish keyboard17:19
FatPhilI've converted 3 slightly broken devices into 2 perfect ones, and a "junker".17:21
FatPhilWell, I've not actually done it, as I can't get a couple of the screws out, but will buy a decent screwdriver set ASAP to complete the swaps I need to so.17:21
FatPhiland then the junker should be usable for a developer, just not for your daily device.17:22
ShadowJKhow broken is the usb?17:26
ShadowJKtraces lifted/missing?17:26
FatPhilTo be honest, I didn't even look. It didn't charge, and the socket was visably out of kilter, so presume lifted17:29
ShadowJKaw17:30
ShadowJKI've got two modem-dead devices17:30
FatPhilwhere in the world are you?17:31
jonwilI am on my 3rd N900 (2 were replaced way back when under warranty)17:32
ShadowJK.fi17:32
jonwilFirst one had a broken display flex PCB (the one with the status multicolor LED and the front camera on it)17:32
jonwilThen the replacement for that ended up with broken USB17:32
FatPhilHelsinki area?17:32
ShadowJKnop17:32
jonwilthen that was replaced under warranty with the third one which I still have17:33
FatPhilI will be in .fi next weekend, and I know a mate has a lab with screwdrivers that will take most of my devices apart (as I did part of the switcheroo last weekend there, before I got the third device).17:34
FatPhilone of the problem with good screwdrivers is that they will strip shitty screws (which did happen, pliers were needed to complete the job)17:35
ShadowJKWell also the philips heads are designed to slip and strip17:35
FatPhilyeah, I have a conical indentation that proves that17:36
ShadowJKtorx makes more sense, but I suspect some greenpeace hippies drove through philips :P17:36
ShadowJKor hex, when hex goes bad you take torx bit and hammer it in17:37
* jonwil has run out of things he can reverse engineer :(17:38
jonwilAnyone with suggestions on what to reverse engineer next please feel free to suggest them :)17:38
FatPhiljonwil: what's the story on rtcom-call-ui?17:39
jonwilwhat about it specifically?17:39
jonwilIts closed source and its doing a lot of stuff which I have never been able to fully work out17:40
jonwilmostly because I dont have any knowledge of telepathy17:40
jonwilShort of hell freezing over and the source code for it appearing somehow (or some genius with both skills in telepathy AND skills in reverse engineering showing up) I dont think we will ever truly know everything that its doing17:41
jonwilis there anything specific you want to know about it?17:42
FatPhilI was just told that it was crashing with a new kernel, so was a candidate for reverse engineering17:43
jonwilok, well as I said, its very complex and hard to reverse engineer17:44
jonwilI need something simpler to fiddle with17:45
jonwilI would fiddle some more with the cellular services daemon but that has been frustrating me too much :(17:48
jonwilEspecially since the cellular modem docs I have are quite a few revisions ahead of the cellmo in the N90017:49
jonwiland since I still cant figure out most of the interface for libisi17:51
*** Martix_ has quit IRC17:51
jonwilmaybe I will go back and take another crack at liblocation...17:54
*** Martix_ has joined #maemo-ssu17:58
*** dhbiker has joined #maemo-ssu18:01
*** Martix_ has quit IRC18:37
*** amizraa has quit IRC18:40
*** jonwil has quit IRC19:03
*** MetalGearSolid has quit IRC19:23
*** lenoch has joined #maemo-ssu19:26
*** LauRoman has quit IRC19:49
*** dos11 has joined #maemo-ssu20:09
*** dos11 is now known as dos1`20:17
*** dos1` is now known as dos120:17
*** sunny_s has quit IRC20:35
*** discopig has quit IRC20:39
*** discopig has joined #maemo-ssu20:40
*** M4rtinK has quit IRC20:41
*** Pali has joined #maemo-ssu20:41
freemangordonPali: can't we just rename "avdet-gpio" to "headphone" in rx51.c and solve our problem?20:50
freemangordonFatPhil: any good idea how to create 'virtual" gpios in the kernel? I was told something like that will be needed in order to have cameras working with DT20:52
Palifreemangordon: it is not about name but about gpio number20:53
freemangordon#define RX51_GPIO_HEADPHONE17720:53
freemangordon#define RX51_JACK_DETECT_GPIO17720:54
freemangordonwhat is wrong with the number?20:54
Palifreemangordon: still "virtual gpios" needs to be in board data or somwhere... so it will be deleted in DT20:54
Palifreemangordon: renaming is not enough20:54
freemangordonPali: ok, please, explain what is the peoblem, I don;t get it20:55
Palionly one can use gpio20:55
freemangordonsound driver opens gpio 17720:55
freemangordonwho else need gpio 177?20:55
Paliand for maemo compatibility you need gpios in omap gpio driver20:55
Paliomap gpio switch driver20:56
freemangordonPali: thus my point20:56
freemangordonmaemo needs "headphone" gpio, ain't?20:56
Paliand in upstream kernel sound driver it using too (for jack detection?)20:56
Paliand maemo needs that gpio exported via omap switch driver20:56
freemangordonoh, I see20:57
Palibut only one driver can use it (snd or omap)20:57
freemangordonwell, we'll need "virtual gpio" driver then20:57
Palibut I patched omap driver to do not fail if cannot open gpio20:57
freemangordonfor sound and for cameras iiuc20:57
Paliand provide fake data to userspace20:57
freemangordoncorrect?20:57
Paliso apps will see them...20:58
freemangordonok, got it20:58
freemangordonPali: where in /sys maemo looks for gpios?20:59
freemangordon"/sys/devices/platform/gpio-switch" ?20:59
Paliyes21:00
Palibut there is already some generic gpio sysfs21:00
freemangordonhmm, can;t we patch omap-gpio driver to make gpios "sharable"?21:00
Paliso maybe we should change omap gpio driver to use that generic sysfs and create symlinks21:00
Palifreemangordon: this is what we should do, but I do not know gpio framework21:01
freemangordonhmm, making symlinks should be easy21:01
freemangordonwhich driver is "ours"?21:02
freemangordongpio-omap?21:02
freemangordonoh, it is gpio-switch21:03
freemangordonlemme see what it does21:04
freemangordonPali: hmm, and how this work in Nokia kernel?21:08
freemangordonPali: WTF, rx51.c in upstream is missing half of the stuff in KP? who and how upstreamed that?!?21:13
Palino idea...21:13
*** amizraa has joined #maemo-ssu21:14
freemangordonOMG: "* n810.c  --  SoC audio for Nokia RX51"21:14
freemangordon:D:D:D21:14
Palibut snd rx51.c using other separate drivers...21:14
Palisee SELECT in Kconfig21:14
freemangordonthe one in KP has select SND_OMAP_SOC_MCBSP more compared to upstream21:16
freemangordonthe others are the same21:16
freemangordonhmm, not, equal thing selected21:17
freemangordonno difference21:17
Paliso all subdrivers are similar and main driver rx51.c is smaller?21:18
freemangordonyep21:18
Palihm, then we maybe missing something21:18
Paliand need to check if tvout detection driver (it is separate in KP) is integrated into rx51.c in upstream or not21:19
freemangordonhmm, I don;t think so21:19
freemangordonseems like upstream has less functionality21:19
Paliah21:19
freemangordonPali: http://pastebin.com/2pSFh79f21:20
freemangordonRX51_JACK_MIC and RX51_JACK_ECI are missing from upstream21:21
Palialso need to look at ECI support which Doc wrote...21:22
freemangordonPali: I guess we should port KP driver21:23
freemangordonand upstream it :(21:24
freemangordonPali: and it seems upstream is missing fmtx support21:27
freemangordonPali: http://pastebin.com/1nDCfPrP21:28
Palifreemangordon: when I have notebook back I can look at it :-)21:30
freemangordonok :)21:30
freemangordonbut deffinitely upstream is missing half of the functionality21:31
Palidoc: I do not have any ECI multibutton headset so I cannot do anything :-(21:31
dos1freemangordon: https://github.com/torvalds/linux/blame/master/sound/soc/omap/rx51.c21:32
dos1https://github.com/torvalds/linux/commit/49100c98359a56ea4e8c9a76e3d625cdb25f25f521:32
dos1"This is a cut down version based on Maemo kernel sources and earlier patchset by Eduardo Valentin et al."21:32
Palifreemangordon: need to look at meego 2.6.37+ kernel if there are not some patches we need21:33
freemangordonPali: :nod:21:33
freemangordondos1: yeah :(21:33
Paliso we will not create new patches which already exists...21:33
freemangordonPali: ok21:33
freemangordonmakes lots of sense :)21:33
*** M4rtinK has joined #maemo-ssu21:34
dos1freemangordon: some fmtx code is there - https://github.com/torvalds/linux/commit/9d7e584b3fb4d9f581b83c0916e10b91de78e66321:37
freemangordonyep, but it is different in nokia kernel aiui21:38
dos1most likely, it seems like updates on that first cut down commit were done independently21:38
freemangordonPali: I think we can remove that "jack gpio" from rx51.c, I guess it is not the driver to decide where to route the sound21:40
freemangordonI wonder why only limited functionality was upstreamed21:41
*** lenoch has quit IRC21:43
Paliok21:45
freemangordonPali: ok, I'll focus on bridgedriver while waiting for your laptop :)21:49
Paliok :-)21:49
freemangordonBTW I almost got it working, but unfortunately as long as it loads baseimage.dof, it spits SYSERROR -10221:49
freemangordonit is something with the voltages I guess, if I remember correctly what I had to do in KP to have it working21:50
freemangordonDSP doesn't work if OPP < 321:50
freemangordon(500 MHz)21:51
*** M4rtinK has quit IRC21:51
Palifreemangordon: can you look at firsts patches in 3.12-rc1-n900 tree? there are some which chaning omap clocks...21:53
Paliand patches are from Skry21:53
Palifreemangordon: and somebody should write some info to LKML about charger patch series, that we really need board hook functions for charger21:57
Paliwhich is needed for charger detection21:57
Paliand this cannot be in DT, because in DT cannot be C/ASM function21:58
freemangordonPali: hmm, I tend to agree with the guys that isp1704 could be treated as regulator21:58
Palithis is still not enough... you need to control gpio plus handle boost mode21:58
freemangordonPali: can't we do regulator_enable/disable?21:59
Palibut this regulator again must be in board code21:59
Palias new function21:59
freemangordonwhy in board code? it can be in bq driver22:00
Palibecause it is board n900 specific22:00
*** DrCode has quit IRC22:00
freemangordonPali: see how ISP deal with vaux322:00
Paliyou need to get data from isp parse them a tell bq2415x what to do22:00
*** nox- has joined #maemo-ssu22:00
Paliand plus enable/disable one gpio22:01
freemangordonin bq driver there could be a check if there is a regulator assigned22:01
freemangordonfrom DT22:01
freemangordonand enable/disable it22:01
Paliand parsing output from isp to bq format is n900 specific22:01
freemangordonthe same for gpio I guess22:01
Paliand gpio too22:01
freemangordonPali: you can have that gpio in DT22:02
freemangordoncorrect?22:02
freemangordonalong with the regulator22:02
freemangordonPali: maybe I should look at the code first :D22:02
*** Martix_ has joined #maemo-ssu22:04
freemangordonPali: I will check if I can convert isp to regulator framework22:04
*** DrCode has joined #maemo-ssu22:05
freemangordonPali: I don;t think we have an option but to do that if we want bq/isp drivers upstreamed22:05
Paliok22:14
Paliand need to check if wl1251 fw is in linux-firmware git tree...22:15
freemangordonit is, but in a different location :D22:16
freemangordoniiuc22:16
Palican you give me link?22:16
Palior check if it is same version as in maemo?22:16
Paliand... need to check licence of bluetooth firmware22:17
freemangordonhttps://lkml.org/lkml/2013/9/24/31622:17
Palianybody here with law skills?22:18
freemangordonPali: hmm, isp1704_charger already using power supply framework, correct?22:21
Paliyes22:25
Palibq2415x too22:25
Palimaybe we can create new driver rx51_charger and move there functions from board code22:26
freemangordonI think there is an easier way, gimme a second22:26
Paliso board charger code will be in new driver rx51_charger22:26
Palithis could be easy22:27
Palijust initialization of charger drivers (platform data) will be in rx51_charger too22:27
freemangordonPali: see http://lxr.free-electrons.com/source/drivers/power/power_supply_core.c#L49722:35
freemangordonwe can define in dt that isp supplies bq22:35
*** okias has joined #maemo-ssu22:35
DocScrutinizer05[2013-10-06 20:31:20] <Pali> doc: I do not have any ECI multibutton headset so I cannot do anything :-(22:36
DocScrutinizer05mere luck that I noticed that, "doc" is nothing that my IRC client highlights22:36
freemangordonand it bq set a listener for POWER_SUPPLY_PROP_CURRENT_MAX prop change22:37
freemangordon*and in22:37
freemangordonPali: that way no external driver needed iiuc22:39
PaliDocScrutinizer05: if you have some ECI headset, you can try to patch kernel too...22:39
DocScrutinizer051704 a regulator? LOL22:39
freemangordonDocScrutinizer05: my bad, I meant a power supply22:39
DocScrutinizer05neither22:39
Palifreemangordon: can you pass mA from isp to bq?22:39
DocScrutinizer05Pali: I don't have any such headset22:40
Paliok, then nothing to do...22:40
freemangordonPali: you can pass a "property change" event I guess, and you can do power_supply_get_by_name("isp1704") (suppplied from dt) and then you can do get_property()22:41
freemangordonPali: sounds sane to you?22:41
*** LauRoman has joined #maemo-ssu22:42
Paliok, waiting for property mA event and reading it is OK22:43
* DocScrutinizer05 watches his toe nails curl22:43
Palibut still we need to enable gpio22:43
freemangordonfrom bq?22:44
Palinow isp calling board function set_power22:44
Paliand it is already in upstream kernel22:45
freemangordonPali: leaving for a while, ,will check what can be done in 15 minutes22:45
DocScrutinizer05isp1707 (1704) is a PHY, not a power supply22:46
DocScrutinizer05those kernel freaks. vibrator is a LED, PHY is a power supply. I wait for CPU becoming a battery22:47
PaliI think that vibrator is LED is only in nokia kernel...22:48
DocScrutinizer05and possibly LCD a audio device22:48
Paliand I bet that isp driver is written by that mr usb man22:49
DocScrutinizer05you know what I'm missing in kernel? A *tiny* bit of decent OO and class hierarchy understanding. Like e.g. it's missing "actor_generic" and "sensor_generic" as basic "object types", and other stuff inheriting from that22:53
DocScrutinizer05but noooo, when we don't have a object class "vibrator2 we look for anything similr, like LED and rape it to service a motor22:55
DocScrutinizer051704 even worse, this has ZILCH in common with a power supply, ABSOLUTELY nothing at all22:56
Paliit is charger...22:57
DocScrutinizer05NO22:57
DocScrutinizer05it is a PHY22:57
DocScrutinizer05it's hardly _connected_ to any charger22:58
DocScrutinizer05nor any power supply22:58
DocScrutinizer05it's a USB bus driver22:59
DocScrutinizer05you as well could call a NIC a charger or power supply22:59
Palidescription:    ISP170x USB Charger driver23:00
DocScrutinizer05even more since it *might* provide PoE and thus actually would supply power, though to external world, not to circuit23:00
Palithis is written in modinfo...23:01
DocScrutinizer05yeah, terrible absolute BULLSHIT23:01
Paligoing to look who wrote that driver23:01
DocScrutinizer05an idiot23:01
okiasDocScrutinizer05: I see lot of optimism :D23:03
DocScrutinizer05eh?23:04
PaliISP1704 USB Charger Detection driver23:04
PaliCopyright (C) 2010 Nokia Corporation23:05
Paliname is hidden23:05
DocScrutinizer05charger DETECTION23:05
Paliand we know why :D23:05
okiastime to git blame :D23:05
DocScrutinizer05it detects wallcharger23:05
DocScrutinizer05that doesn't make it a charger, nor a power supply23:05
Palido you have full git repo of kernel near?23:06
okiasno :(23:06
Paliok, going to look at linus git web log23:07
DocScrutinizer05confirms my take that it must have been an idiot who reads "charger detection" and thinks "duh, a charger that does detect, so it's >>description:    ISP170x USB Charger driver<<"23:07
DocScrutinizer05with this logic ALS is a LED23:08
Palipower_supply: Add isp1704 charger detection driver23:09
DocScrutinizer05since it's light detection23:09
PaliNXP ISP1704 is Battery Charging Specification 1.0 compliant USB transceiver. This adds a power supply driver for ISP1704 and ISP1707 USB transceivers.23:09
PaliHeikki Krogerus <ext-heikki.krogerus@nokia.com>23:09
Palicommit: ec46475f3e3163dd80bfee086fa71b36455ecc0b23:10
Paliyou can contact that person :-)23:10
DocScrutinizer05to do what?23:10
DocScrutinizer05tell him that ISP170x do not supply power?23:11
DocScrutinizer05or tell him that it definitely doesn't CHARGE23:11
Paliwhatever you want :P23:12
DocScrutinizer05meh23:12
Paliso because of nokia...23:12
DocScrutinizer05not because of nokia23:12
DocScrutinizer05>>ISP1704 USB Charger Detection driver<< sounds correct23:13
DocScrutinizer05but been already too long and complicated for ADHS of those other guys23:13
DocScrutinizer05ISP1704 USB Charger Detection driver   does exactly one thing: detect Nokia fastcharger via D+/- short23:14
DocScrutinizer05NOTHING else23:14
DocScrutinizer05well, s/driver//23:15
DocScrutinizer05I dunno what the driver does, but I know what charger detection in 1707 does23:15
*** Pali has quit IRC23:16
DocScrutinizer05>>description:    ISP170x USB Charger driver<<"  !=  >>ISP1704 USB Charger Detection driver<<23:16
DocScrutinizer05first one suggests 1707 is a battery charger, which it clearly isn't23:17
DocScrutinizer05it's not a charger, it's a detector23:17
DocScrutinizer05basically a derived object of class sensor_generic23:18
freemangordonDocScrutinizer05: kowing what it is doesn't help much with the upstreaming :)23:20
freemangordonknowing even23:20
DocScrutinizer05not any member of class internal_function_generic, and particularly not of the subclass of that called power_management23:20
freemangordonhmm, where's pali gone?23:20
DocScrutinizer05Pali has left this server (Quit: xchat sucks and needs a kick).23:21
freemangordonDocScrutinizer05: any clue what GPIO was Pali talking about?23:21
DocScrutinizer05when?23:21
freemangordon<Pali> but still we need to enable gpio23:21
DocScrutinizer05maybe he meant the output of 1707?23:22
DocScrutinizer05err nope that is always active afaik23:22
freemangordonDocScrutinizer05: which IC is that on the schematic?23:22
DocScrutinizer05maybe he meant the input of bq2415023:22
freemangordonN1140?23:23
DocScrutinizer05which one? 1707?23:23
freemangordonbq2415023:23
freemangordonand 1707 as well23:23
freemangordonI want to look at how are thoose connected before making conclusions/taking decisions23:24
DocScrutinizer0524150 = N114023:24
freemangordonhmm, I see no input gpio there23:24
DocScrutinizer051707 = D428023:25
freemangordonthanks23:26
DocScrutinizer05CHRG_DET23:26
DocScrutinizer05-> OTG23:26
DocScrutinizer0524150 OTG can be set to different modes23:26
DocScrutinizer05you +could* call bq24150 OTG a GPIO23:27
freemangordonhmm, ok, makes sense then23:27
DocScrutinizer05funny enough on 1707 the CHGR_DET is marked as IO ( <> )23:28
freemangordonyep23:28
DocScrutinizer05I wouldn't know how that can act as input23:28
DocScrutinizer05afaik it's an (open collector?) output only23:28
*** lenoch has joined #maemo-ssu23:28
DocScrutinizer05but you also can program it maybe, to either stay inactive or actually signal D+- short23:29
DocScrutinizer05all this is only used during emergency charge anyway23:30
DocScrutinizer05so you basically can ignore it23:30
DocScrutinizer051707 sends "D+- short" message via ULPI bus to musb-hdrc core23:30
freemangordongpio_set_value(RX51_USB_TRANSCEIVER_RST_GPIO, on);23:31
freemangordon#define RX51_USB_TRANSCEIVER_RST_GPIO6723:31
DocScrutinizer05ooh, PHY reset23:31
freemangordon"ISP_RST"23:31
DocScrutinizer05I don't see such reset on 170723:32
freemangordonCHIP_SEL23:32
freemangordonor DIR?23:33
freemangordonyep, CHIP_SEL23:33
freemangordonthis should be a part of ISP driver IMO23:34
DocScrutinizer05chip_sel is not reset23:34
DocScrutinizer05afaik23:35
freemangordonwell, don;t ask me23:35
freemangordon:)23:35
freemangordonI didn't write that code23:35
DocScrutinizer05NB schem tells "GAIA HS-USB transceiver" which is bogus legacy23:35
DocScrutinizer05nah, schem as well has "ISP_RST"23:36
freemangordondo you have the datasheet? (I guess you have it)23:36
DocScrutinizer05which might have been the case when it been GAIA's PHY and not a dedicated 170723:37
freemangordonok, so for the log:23:37
DocScrutinizer051707 datasheet not available, you need to use 1704 and keep in minf that one pin has switched active polarity23:37
DocScrutinizer05mind*23:37
freemangordonISP1707 CHIP_SEL GPIO could be provided for either board code or DT, and set_power board function actually has to be in the ISP driver code23:38
DocScrutinizer05http://www.google.de/search?q=isp170423:38
freemangordonso, if we have that provided (by either board code or DT), set it in the driver, instead of calling set_power23:39
freemangordonyep, deffinitely CHIP_SEL23:40
DocScrutinizer05 when either the CHIP_SEL or CHIP_SEL_N pin is deasserted, ULPI pins will be i n3-state and the ISP1704A is in power-down mode; both CHIP_SEL and CHIP_SEL_ Nmust be asserted for the ULPI interface to operate normally; when not in use, connect t oVCC(I/O )plain input23:41
freemangordonhmm, putting pins in high-impedance is not a reset in my book23:42
DocScrutinizer05nope23:42
freemangordonhowever23:42
DocScrutinizer05definitely not23:42
freemangordonoh, power-down23:42
freemangordonwell, we can fix the naming23:43
DocScrutinizer05yep, the schematics has an erratum there23:44
DocScrutinizer05CHGR_DET_EN_N is at gnd level, hardwired23:46
DocScrutinizer05 automatic charger detect enable; connect to VCC when the automatic charger detection is not required; connect to GND when the automatic charger detection is needed i nperipheral mode23:47
freemangordonhmm, this time it seems uptream devs have a point23:47
*** M4rtinK has joined #maemo-ssu23:47
DocScrutinizer05hmm?23:48
freemangordonisp driver has (or can acwuire) all the needed data without having to call the board code23:48
freemangordon*acquire23:48
DocScrutinizer05nfc23:49
DocScrutinizer05CHGR_DET   active-HIGH signal to start high current charging; when not in use, leave this pin ope n   active-HIGH output; 5 V tolerant; external 100 kΩ pull-down resistor23:49
freemangordonwill discuss it with Pali when he is back online23:50
DocScrutinizer05again, this is only relevant for emergency-charging23:50
DocScrutinizer051707 sends "D+- short" message via ULPI bus to musb-hdrc core23:51
DocScrutinizer05and this is what you see in the sysnode for "charger"23:52
DocScrutinizer05>> /sys/devices/platform/musb_hdrc/charger  (SIC!)23:53
DocScrutinizer05musb_hdrc is the only correct location for this23:53
DocScrutinizer05no friggin powersupply or even charger23:54
*** Martix_ has quit IRC23:57
DocScrutinizer05and this is the reason why musb-hdrc driver needs to be monolithic (no module), since charger detect aka D+- short detect needs to get done very early in boot to not interrupt charging23:57
freemangordoncool https://lkml.org/lkml/2013/10/6/12723:57

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!