All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: linux-omap@vger.kernel.org, Pavan Savoy <pavan_savoy@ti.com>
Cc: LAK <linux-arm-kernel@lists.infradead.org>, linux-pm@vger.kernel.org
Subject: Ti-st suspend/resume hooks
Date: Fri, 09 Aug 2013 15:14:11 +0530	[thread overview]
Message-ID: <5204B9EB.4020809@gmail.com> (raw)

Hi,

Our i.Mx6 based platform has a wl12xx chip and the ti-st driver is in 
use. When the system goes to suspend, the st_kim module fails to suspend 
giving out -EOPNOTSUPP [1], which is quite evident from the the missing 
suspend/resume hooks in the wilink_platform_data. [2]

Are there any ways to make this ti-st driver suspend/resume aware?

Thanks,
Vikram

[1] http://lxr.linux.no/linux+v3.10.5/drivers/misc/ti-st/st_kim.c#L833

[2] 
http://lxr.linux.no/linux+v3.10.5/arch/arm/mach-omap2/board-omap4panda.c#L58

P.S: I'm not subscribed to the list. Please keep me Cc'd.

WARNING: multiple messages have this Message-ID (diff)
From: vikram186@gmail.com (Vikram Narayanan)
To: linux-arm-kernel@lists.infradead.org
Subject: Ti-st suspend/resume hooks
Date: Fri, 09 Aug 2013 15:14:11 +0530	[thread overview]
Message-ID: <5204B9EB.4020809@gmail.com> (raw)

Hi,

Our i.Mx6 based platform has a wl12xx chip and the ti-st driver is in 
use. When the system goes to suspend, the st_kim module fails to suspend 
giving out -EOPNOTSUPP [1], which is quite evident from the the missing 
suspend/resume hooks in the wilink_platform_data. [2]

Are there any ways to make this ti-st driver suspend/resume aware?

Thanks,
Vikram

[1] http://lxr.linux.no/linux+v3.10.5/drivers/misc/ti-st/st_kim.c#L833

[2] 
http://lxr.linux.no/linux+v3.10.5/arch/arm/mach-omap2/board-omap4panda.c#L58

P.S: I'm not subscribed to the list. Please keep me Cc'd.

             reply	other threads:[~2013-08-09  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  9:44 Vikram Narayanan [this message]
2013-08-09  9:44 ` Ti-st suspend/resume hooks Vikram Narayanan

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=5204B9EB.4020809@gmail.com \
    --to=vikram186@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavan_savoy@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: link
Be 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.