**** BEGIN LOGGING AT Tue Aug 09 02:59:58 2016
Aug 09 03:32:34 <DocScrutinizer05> PaulFertser: http://wiki.openmoko.org/index.php?title=USB_Product_IDs&diff=108805&oldid=108804  I didn't prepare/send any patch
Aug 09 03:53:33 <DocScrutinizer05> PaulFertser: sorry typo! 0x60fC is the correct ID
Aug 09 03:54:40 * DocScrutinizer05 yawns, mumbles 'nitynite' and waves, then heads out
Aug 09 22:41:46 <DocScrutinizer05> PaulFertser: you're around?
Aug 09 22:43:18 <DocScrutinizer05> PaulFertser: sorry I didn't intend to sound brash in my mail when I said "Paul will send the patch to upstream"
Aug 09 22:45:13 <DocScrutinizer05> PaulFertser: anyway I hope my webpage edits help a bit
Aug 10 00:36:19 <stdint> I have some problem with pin ctrl at am335x
Aug 10 00:37:20 <stdint> for example, 0x10 (PIN_INPUT_PULLDOWN | MUX_MODE7) I know the first number is the index of that pin
Aug 10 00:38:47 <stdint> but I have no idea where they are defined in document, is there  some formula to calculate that index?
Aug 10 00:41:18 <DocScrutinizer05> tricky
Aug 10 00:41:28 <DocScrutinizer05> the docs are puzzling
Aug 10 00:44:12 <DocScrutinizer05> generally you got a pin NAME like GPIO_168, then there's a block of registers for all GPIO *somewhere* in address range, and the 0x10 is basically used as an index into that addr range like $OFFSET + $PIN-INDEX * sizeof(REGISTERS-PER-GPIO)
Aug 10 00:44:35 <DocScrutinizer05> *afaik*
Aug 10 00:44:51 <DocScrutinizer05> depends on your macros you use
Aug 10 00:47:04 <DocScrutinizer05> the macros does GPIO_168  -> $OFFSET + $PIN-INDEX * sizeof(REGISTERS-PER-GPIO) => 0xff4500 + 168 * 64
Aug 10 00:47:11 <DocScrutinizer05> or somesuch
Aug 10 00:47:38 <DocScrutinizer05> OFFSET and sizeof(REGISTERS-PER-GPIO) are defined in some .h for your SoC
Aug 10 00:47:59 <stdint> DocScrutinizer05, I see, I would check it
Aug 10 00:48:04 <DocScrutinizer05> just like the macro using those
Aug 10 00:48:33 <stdint> but it is seems that the some pins could be mux functions are not be placed at GPIO chapter at Ti doc
Aug 10 00:48:48 <DocScrutinizer05> DeviceTree *might* also come in, I'm not savvy about that stuff
Aug 10 00:49:50 <DocScrutinizer05> well, you first need to switch the pin to GPIO mode via pinmux
Aug 10 00:50:17 <stdint> I know how to do that
Aug 10 00:50:17 <DocScrutinizer05> basically all pins have 3 or 4 alternative functions at least
Aug 10 00:50:35 <DocScrutinizer05> one is GPIO_nnn
Aug 10 00:50:53 <DocScrutinizer05> I guess for GPIO_nnn the above scheme always applies
Aug 10 00:51:07 <stdint> but I don't the map between those special pin to gpio. For example USB1_DP, I can't find which GPIO it is
Aug 10 00:51:19 <DocScrutinizer05> all GPIO_nnn are also the same type, more or less
Aug 10 00:51:52 <DocScrutinizer05> there's a list of *all* pins in the docs, with each pin listed all functions it has
Aug 10 00:52:26 <DocScrutinizer05> look up USB1_DP there, check what GPIO_nnn it has as alternative
Aug 10 00:54:55 <stdint> DocScrutinizer05, maybe I use the wrong document? I use the spruh73n.pdf
Aug 10 00:54:58 <DocScrutinizer05> the docs _are_ puzzling. and a friggin 3000+ pages
Aug 10 00:55:13 <stdint> actually 5041 pages
Aug 10 00:55:19 <DocScrutinizer05> sorry, I'm with 35/37, no 33
Aug 10 00:55:57 <stdint> OK, let me check that chip, maybe it would be in the some chapter
Aug 10 00:56:17 <stdint> could you tell me what is the page number in your document?
Aug 10 00:57:33 <DocScrutinizer05> http://wstaw.org/m/2016/08/10/plasma-desktopUb2277.png 
Aug 10 00:58:11 <DocScrutinizer05> http://wstaw.org/m/2016/08/10/plasma-desktoplj2277.png
Aug 10 00:59:28 <DocScrutinizer05> HTH
Aug 10 01:00:52 <DocScrutinizer05> omap3525-hirel.pdf  aka SPRS599D
Aug 10 01:01:19 <DocScrutinizer05> p85 ff
Aug 10 01:02:00 <DocScrutinizer05> did I already mention the docs _are_ puzzling like hell?
Aug 10 01:05:44 <stdint> DocScrutinizer05, thank you very much
Aug 10 01:05:54 <DocScrutinizer05> yw :-)
Aug 10 01:06:59 <DocScrutinizer05> stdint: btw
Aug 10 01:07:10 <DocScrutinizer05> I just notice I told incorrect
Aug 10 01:07:45 <DocScrutinizer05> in >>0x10 (PIN_INPUT_PULLDOWN | MUX_MODE7)<< the 0x10 most likely is NOT the same like GPIO_010
Aug 10 01:08:06 <DocScrutinizer05> this must be yet another pin index
Aug 10 01:09:11 <DocScrutinizer05> prolly in context of pinmux
Aug 10 01:09:44 <DocScrutinizer05> did I already mention the freakin docs are *really* puzzling like hell?
Aug 10 01:16:50 <DocScrutinizer05> apropos pinmux, do you know the software of that name from TI?
Aug 10 01:16:58 <DocScrutinizer05> it sometimes is useful
Aug 10 01:18:02 <DocScrutinizer05> it's basically just that table I screenshotted above, plus interactivity, and it generates code for pinmux to configure the pins accordingly
Aug 10 01:18:17 <DocScrutinizer05> so it has to know about pin 0x10 too
Aug 10 01:28:38 <DocScrutinizer05> (pinmux prog) alas for OMAP3 you need the windows-only version
Aug 10 01:42:15 <stdint> DocScrutinizer05, I don't know that, which one?
Aug 10 01:42:41 <DocScrutinizer05> search for TI pinmux
Aug 10 01:42:58 <stdint> http://www.ti.com/tool/PINMUXTOOL
Aug 10 01:43:02 <DocScrutinizer05> http://www.ti.com/tool/PINMUXTOOL
Aug 10 01:43:03 <stdint> I see thank you
Aug 10 01:44:00 <DocScrutinizer05> wow, cloud version supports am335x
Aug 10 01:44:09 <stdint> yes I found it
Aug 10 01:44:13 <DocScrutinizer05> you're lucky
Aug 10 01:44:20 <stdint> I don't need to find a windows machine
Aug 10 01:44:25 <DocScrutinizer05> :-)
**** ENDING LOGGING AT Wed Aug 10 02:59:58 2016