From: Santosh Shilimkar <santosh.shilimkar@ti.com> To: balbi@ti.com Cc: linux-omap@vger.kernel.org, khilman@deeprootsystems.com, paul@pwsan.com, tony@atomide.com, sourav.poddar@ti.com, vaibhav.bedia@ti.com, linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC/RFT PATCH 0/2] SERIAL: OMAP: Remove idle handling from driver Date: Mon, 18 Feb 2013 16:25:58 +0530 [thread overview] Message-ID: <512208BE.7060207@ti.com> (raw) In-Reply-To: <20130218104541.GD32688@arwen.pp.htv.fi> On Monday 18 February 2013 04:15 PM, Felipe Balbi wrote: > On Mon, Feb 18, 2013 at 12:42:16PM +0200, Felipe Balbi wrote: >> Hi, >> >> On Mon, Feb 18, 2013 at 03:55:33PM +0530, Santosh Shilimkar wrote: >>>>> I wonder what are your ideas to sort that part out, I mean, how do you >>>>> plan to implement ->set_wake() for the tty port ?" >>>> >>>> [1] http://marc.info/?l=linux-omap&m=136093334914275&w=2 >>>> >>> The main need for uart wakeup is the io_ring() trigger and that needs >>> to happen via generic pin control API. SYSC wakeup bit isn't something >>> needs to be toggled so that can be decoupled. So again the idea is >>> to make SYSC handling transparent to UART drivers and let driver toggle >>> the io_ring() based on ->set_wake() as it is done today. >> >> We're either reading different code bases or not understanding each >> other. Currently this is how ->set_wake() is implemented: >> >> serial_omap_set_wake() >> serial_omap_enable_wakeup() >> omap_uart_enable_wakeup() >> omap_hwmod_enable_wakeup() >> if (SYSC_HAS_ENAWAKEUP) { /* true for UART */ >> _enable_wakeup() There is no need to toggle this one. It can be set once and left as is. >> _write_sysconfig() >> } >> set_idle_ioring_wakeup() So this is the part, we need to hookup with pads. >> if (!oh->mux || !oh->mux->enabled) >> return; >> >> If I read the code correctly there's nothing setting oh->mux during DT >> boot. The only caller to omap_hwmod_mux_init() (which allocates and >> returns omap_hwmod_mux_info pointer) is >> arch/arm/mach-omap2/devices.c::omap4_keyboard_init(). This has nothing > > actually arch/arm/mach-omap2/serial.c::omap_serial_init_port() also > calls that, but it's also not used during DT boots. > DT boot, all the function pointers are broken so wakeup as well as slave idle-mode is broken. Nothing new here. Serial file does set the pads as you noticed and this is what can be offloaded to generic pint control which can triggered from driver. Regards, Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar) To: linux-arm-kernel@lists.infradead.org Subject: [RFC/RFT PATCH 0/2] SERIAL: OMAP: Remove idle handling from driver Date: Mon, 18 Feb 2013 16:25:58 +0530 [thread overview] Message-ID: <512208BE.7060207@ti.com> (raw) In-Reply-To: <20130218104541.GD32688@arwen.pp.htv.fi> On Monday 18 February 2013 04:15 PM, Felipe Balbi wrote: > On Mon, Feb 18, 2013 at 12:42:16PM +0200, Felipe Balbi wrote: >> Hi, >> >> On Mon, Feb 18, 2013 at 03:55:33PM +0530, Santosh Shilimkar wrote: >>>>> I wonder what are your ideas to sort that part out, I mean, how do you >>>>> plan to implement ->set_wake() for the tty port ?" >>>> >>>> [1] http://marc.info/?l=linux-omap&m=136093334914275&w=2 >>>> >>> The main need for uart wakeup is the io_ring() trigger and that needs >>> to happen via generic pin control API. SYSC wakeup bit isn't something >>> needs to be toggled so that can be decoupled. So again the idea is >>> to make SYSC handling transparent to UART drivers and let driver toggle >>> the io_ring() based on ->set_wake() as it is done today. >> >> We're either reading different code bases or not understanding each >> other. Currently this is how ->set_wake() is implemented: >> >> serial_omap_set_wake() >> serial_omap_enable_wakeup() >> omap_uart_enable_wakeup() >> omap_hwmod_enable_wakeup() >> if (SYSC_HAS_ENAWAKEUP) { /* true for UART */ >> _enable_wakeup() There is no need to toggle this one. It can be set once and left as is. >> _write_sysconfig() >> } >> set_idle_ioring_wakeup() So this is the part, we need to hookup with pads. >> if (!oh->mux || !oh->mux->enabled) >> return; >> >> If I read the code correctly there's nothing setting oh->mux during DT >> boot. The only caller to omap_hwmod_mux_init() (which allocates and >> returns omap_hwmod_mux_info pointer) is >> arch/arm/mach-omap2/devices.c::omap4_keyboard_init(). This has nothing > > actually arch/arm/mach-omap2/serial.c::omap_serial_init_port() also > calls that, but it's also not used during DT boots. > DT boot, all the function pointers are broken so wakeup as well as slave idle-mode is broken. Nothing new here. Serial file does set the pads as you noticed and this is what can be offloaded to generic pint control which can triggered from driver. Regards, Santosh
next prev parent reply other threads:[~2013-02-18 10:54 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-15 12:06 [RFC/RFT PATCH 0/2] SERIAL: OMAP: Remove idle handling from driver Santosh Shilimkar 2013-02-15 12:06 ` Santosh Shilimkar 2013-02-15 13:03 ` a0131647 2013-02-15 13:03 ` a0131647 2013-02-15 13:07 ` Felipe Balbi 2013-02-15 13:07 ` Felipe Balbi 2013-02-15 13:08 ` Felipe Balbi 2013-02-15 13:08 ` Felipe Balbi 2013-02-15 13:42 ` a0131647 2013-02-15 13:42 ` a0131647 2013-02-15 13:50 ` Santosh Shilimkar 2013-02-15 13:50 ` Santosh Shilimkar 2013-02-18 10:04 ` Santosh Shilimkar 2013-02-18 10:04 ` Santosh Shilimkar 2013-02-18 10:10 ` Felipe Balbi 2013-02-18 10:10 ` Felipe Balbi 2013-02-18 10:11 ` Felipe Balbi 2013-02-18 10:11 ` Felipe Balbi 2013-02-18 10:25 ` Santosh Shilimkar 2013-02-18 10:25 ` Santosh Shilimkar 2013-02-18 10:42 ` Felipe Balbi 2013-02-18 10:42 ` Felipe Balbi 2013-02-18 10:45 ` Felipe Balbi 2013-02-18 10:45 ` Felipe Balbi 2013-02-18 10:55 ` Santosh Shilimkar [this message] 2013-02-18 10:55 ` Santosh Shilimkar 2013-02-18 11:13 ` Felipe Balbi 2013-02-18 11:13 ` Felipe Balbi 2013-02-18 14:36 ` Santosh Shilimkar 2013-02-18 14:36 ` Santosh Shilimkar
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=512208BE.7060207@ti.com \ --to=santosh.shilimkar@ti.com \ --cc=balbi@ti.com \ --cc=khilman@deeprootsystems.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=paul@pwsan.com \ --cc=sourav.poddar@ti.com \ --cc=tony@atomide.com \ --cc=vaibhav.bedia@ti.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.