narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
nemunaire has quit [Ping timeout: 252 seconds]
return0e has quit [Ping timeout: 240 seconds]
return0e has joined #linux-amlogic
nemunaire has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 244 seconds]
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
Darkmatter66 has quit [Remote host closed the connection]
Barada has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
ldevulder_ is now known as ldevulder
ldevulder has quit [Ping timeout: 245 seconds]
ldevulder has joined #linux-amlogic
nsaenz has quit [Ping timeout: 245 seconds]
nashpa_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
sputnik_ has joined #linux-amlogic
nashpa_ is now known as nashpa
afaerber has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
Elpaulo has quit [Ping timeout: 246 seconds]
_whitelogger has joined #linux-amlogic
Barada has quit [Quit: Barada]
<narmstrong> xdarklight: hi, do you recall how you fixed occurence of https://pastebin.com/N1PhwwBf ?
<narmstrong> i recall having these on GXL
<narmstrong> but at some point it was fixed
<narmstrong> (it's for G12A)
<xdarklight> narmstrong: I believe it was you who found out that we need to set that 0x20 value which is why we have phy-meson-gxl-usb3
<narmstrong> xdarklight: hmm
<narmstrong> oh
<narmstrong> interesting, I set the usb3 regs :-/
<xdarklight> :/
<xdarklight> I think "phy-meson-gxl-usb3" is not really a PHY by the way
<narmstrong> xdarklight: yeah, it's kind of a glue for the usb3 phy, on G12A it talks to a true USB3 PHY
<xdarklight> yep
<xdarklight> we should probably re-implement it as dwc3-amlogic
<narmstrong> this one hasn't changed, except the USB3 PHY :-p
<xdarklight> and have a real G12A USB3 PHY driver
<narmstrong> yeap
<xdarklight> and the USB2 PHY obviously
<xdarklight> G12A has a new USB2 PHY
<narmstrong> usb2 phy has changed, and it split in two...
<narmstrong> now it's a glue, and the phy registers are separated
<narmstrong> so yeah, the best would be to have a dwc3-amlogic glue to setup this and have true PHY drivers
<xdarklight> narmstrong: re your G12A errors: maybe you need to set 0x20 on the dwc3 instance as well: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/usb/dwc3.txt#L83
<xdarklight> (on GXL and GXM the dwc3 registers default to 0x20 for that value, so we don't have it there)
<narmstrong> let's check !
<xdarklight> narmstrong: also do you have the reset line hooked up?
<narmstrong> xdarklight: yep, each usb2 phy also have separate reset lines aswell
<xdarklight> finally!
<narmstrong> ok, this does not help, thanks for helping...
Elpaulo has joined #linux-amlogic
Elpaulo1 has joined #linux-amlogic
Elpaulo has quit [Read error: No route to host]
Elpaulo1 is now known as Elpaulo
garstyciuks has joined #linux-amlogic
<garstyciuks> hey guys, I'm working on porting a kernel module to run on odroid C2, and hit an issue - I can't get GPIO interrupts to work at all
<garstyciuks> there's even no "edge" in /sys/class/gpio/.../ appearing after GPIOs are exported to user space
<garstyciuks> I have verified that running the 3.16 kernel that odroid officially supports, the 'edge' appears to be usable
<garstyciuks> I'm using 4.19.14 kernel version on armbian
<garstyciuks> the actual issue the kernel module I'm working on has is the gpiod_to_irq returns -6 (ENXIO 6 No such device or address), the GPIO itself is usable as input
<garstyciuks> so I just can't figure out how to attach a rising edge interrupt to the pin...
garstyciuks has quit [Ping timeout: 256 seconds]
drieschel has joined #linux-amlogic
afaerber has quit [Quit: Leaving]
garstyciuks has joined #linux-amlogic
<xdarklight> garstyciuks: the mainline GPIO driver doesn't have GPIO IRQ support yet
<xdarklight> most of the code is there, but the final .to_irq call is missing because there was a discussion (for which I believe there was never a conclusion) how to model the IRQ domain inside the GPIO controller
chewitt has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
<garstyciuks> hey, yeah, I think I found the discussion
<garstyciuks> I saw 'platform_get_irq' mentioned as an alternative way to get the interrupt to use for request_irq call
<garstyciuks> in my dt overlay, I have: interrupt-parent = <&gpio_intc>; interrupts = <109 0>;
<garstyciuks> platform_get_irq(pdev, 0) in the module probe then gives me some valid value, I haven't yet been able to test it, don't have access to the hardware at this time :)
<garstyciuks> but anyway, would this be the correct way to hook up a GPIO interrupt while gpio_to_irq is not implemented ?
<garstyciuks> I took 109 value from https://dn.odroid.com/S905/DataSheet/S905_Public_Datasheet_V1.1.4.pdf page 86, this is for GPIOX_3 pin
<xdarklight> garstyciuks: 109 seems correct
<xdarklight> garstyciuks: but I don't think you can use "109 0" in the .dts
<xdarklight> (the irq-meson-gpio driver forbids using IRQ_TYPE_EDGE_BOTH though)
<garstyciuks> I'm interested in IRQ_TYPE_EDGE_RISING, however, that gave me some 'type mismatch' error logged
<garstyciuks> when loading the overlay
<garstyciuks> IRQ_TYPE_LEVEL_LOW as in the example was loaded successfully as well
<garstyciuks> I don't have access to the log at the moment to tell the exact error that was printed in dmesg...
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
afaerber has joined #linux-amlogic
Elpaulo has quit [Read error: No route to host]
Elpaulo has joined #linux-amlogic
nemunaire has quit [Ping timeout: 252 seconds]
garstyciuks has quit [Ping timeout: 256 seconds]