On Mon, May 07, 2018 at 10:50:32AM -0700, Tony Lindgren wrote: > * Johan Hovold <johan@xxxxxxxxxx> [180507 16:36]: > > On Mon, May 07, 2018 at 08:45:15AM -0700, Tony Lindgren wrote: > > > Hi, > > > > > > * Johan Hovold <johan@xxxxxxxxxx> [180507 03:03]: > > > > On Fri, May 04, 2018 at 01:42:13PM +0200, Sebastian Reichel wrote: > > > > Note that serdev not enabling runtime pm for controllers is roughly > > > > equivalent to setting the .ignore_children flag, which is what we do for > > > > i2c and spi controller, and possibly what we want here too. > > > > > > We currently don't idle serdev at all even if not in use. What > > > I noticed is if I have these in my .config: > > > > > > CONFIG_SERIAL_DEV_BUS=y > > > CONFIG_SERIAL_DEV_CTRL_TTYPORT=y > > > > > > And no hci_serdev.ko driver loaded, then the 8250 port still stays > > > active and there are no sysfs entries to idle it. > > > > Sounds like the 8250_omap driver is doing something funky. Why would > > there not be any sysfs attributes to control runtime pm? > > I don't know, they are there for the ports that don't have any > serdev device. But if there is a serdev child node, the sysfs > disappear for the 8250 port like it's /dev/ttyS* entry. That is > even with no hci_serdev.ko loaded :) It sounds to me like you have a udev rule that's matching on TTY devices and setting an autosuspend timeout that allows the controller to runtime suspend. Is that so? With serdev such a rule would no longer be sufficient as it would no longer configure all controllers. You can always set the autosuspend directly through the platform device node, for example: /sys/bus/platform/devices/481aa000.serial But the point is, we really don't want the runtime PM behaviour to be dependent on the presence of such rules. The serial controllers should always be idle when not in use (unless overridden by user space). > > > Are you seeing this with your series? > > > > I'm using omap-serial (on BBB) and like 8250_omap, the driver disables > > runtime pm at probe by setting a negative autosuspend timeout. > > Hmm I though we now have both 8250_omap and serial-omap behave the > same way for PM. It looks like they've been implemented the same way (e.g. the negative autosuspend timeout). > > Changing this through sysfs causes the serial controller to runtime > > suspend, but something is not right in my setup as it doesn't wake up on > > incoming data. > > Do you have also a /dev/ttyO* entry created for the serdev port? No, serdev claims the port and no tty device is created. > > I'd say the omap drivers are broken; the controller should definitely > > idle when the port is closed (whether using serdev or not) without > > having to fiddle with sysfs. > > This is happening for the non-serdev ports for sure. FYI, there is > one patch needed for omap4 to idle unused ports that I posted > few days ago: > > [PATCHv3] serial: 8250: omap: Fix idling of clocks for unused uarts > > But the serdev port is never idled, even if unused. With the negative autosuspend set in both omap drivers probe functions, this is the expected behaviour. Which I think we must fix. > Can you check your serdev port clkctrl reg with rwmem or similar > tool when it's idle? > > You can do it with: > > rwmem -s32 0x44e004b4 # uart 1 on l4_wkup > rwmem -s32 0x44e0006c+0x10 # uart 2 - 5 on l4_per > rwmem -s32 0x44e00038 # uart 6 on l4_per > > And here's what I have on my bbb with 8250_omap: > > 0x44e004b4 = 0x00000002 > 0x44e0006c = 0x00030000 > 0x44e00070 = 0x00030000 > 0x44e00074 = 0x00030000 > 0x44e00078 = 0x00030000 > 0x44e00038 = 0x00030000 > > So all disabled except for the console UART. On BBB with omap-serial I have: 0x44e004b4 = 0x2 (uart 1, console, open) 0x44e0006c = 0x2 (uart 2, serdev, closed) 0x44e00070 = 0x30000 (uart 3, disabled in DT) 0x44e00074 = 0x30000 (uart 4, disabled in DT) 0x44e00078 = 0x2 (uart 5, serdev, closed) 0x44e00038 = 0x2 (uart 6, ttyO5, closed) So no enabled and closed port is idle, whether using serdev or not. Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
