devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Jassi Brar <jassisinghbrar@gmail.com>, Suman Anna <s-anna@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Keerty J <j-keerthy@ti.com>
Subject: Re: [PATCH v3 0/3] soc: ti: Introduce wkup_m3_ipc driver
Date: Wed, 2 Dec 2015 14:29:53 -0600	[thread overview]
Message-ID: <565F54C1.8090407@ti.com> (raw)
In-Reply-To: <20151020161843.GE3078@atomide.com>

Hi,
On 10/20/2015 11:18 AM, Tony Lindgren wrote:
> Hi all,
>
> * Dave Gerlach <d-gerlach@ti.com> [150922 17:20]:
>> Hi,
>> This series is version 3 of the code to introduce a wkup_m3_ipc driver
>> to handle communication between the MPU and Cortex M3 present on TI AM335x
>> and AM437x SoCs. v2 of this series can be found at [1]. Only patch 3
>> has been changed based on a request from Tony and a few cleanups:
>>
>> - Rather than exporting all of the functionality of the driver, added
>>    wkup_m3_ipc_get and wkup_m3_ipc_put to allow users to just get a handle
>>    containing an ops structure for use.
>>
>> - Changed all ops (previously exported functions) to take pointer to
>>    struct wkup_m3_ipc as an argument now that user code will get this
>>    from wkup_m3_ipc_get.
>>
>> - General cleanup to probe function
>>
>> - Added MODULE_DEVICE_TABLE so driver can probe automatically.
>>
>> The series containing the DT nodes can be found here [2]. The actual dt
>> nodes for wkup_m3_ipc (last two patches) have been merged but discussion
>> is still open for the ti,mbox-send-noirq flag patches and depends on the
>> comments provided for the omap-mailbox change presented in patch 1 of
>> this series.
>>
>> A full branch containing all necessary PM code for both am335x and am437x
>> has been pushed here [3] to provide a big picture view of the plan for
>> this series.
>>
>> This driver relies on the firmware at [4] in the next-upstream branch
>> being present in /lib/firmware in the rootfs or built in to the kernel.
>
> Anybody got comments on this one? Should I pick up this series or
> what's the plan?

Now that Patch 1 has been merged [1] can patch 2 and 3 be picked up? 
These apply cleanly on v4.4-rc3.

Regards,
Dave

[1] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8e3c5952144f045a0c81bf674d3f5e1d9aafceb7

>
> Regards,
>
> Tony
>
>
>> [1] https://lkml.org/lkml/2015/7/17/797
>> [2] https://lkml.org/lkml/2015/7/17/813
>> [3] https://github.com/dgerlach/linux-pm/tree/pm-v4.3-rc1-amx3-suspend
>> [4] https://git.ti.com/ti-cm3-pm-firmware
>>
>> Dave Gerlach (3):
>>    mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle
>>    Documentation: dt: add bindings for TI Wakeup M3 IPC device
>>    soc: ti: Add wkup_m3_ipc driver
>>
>>   .../devicetree/bindings/mailbox/omap-mailbox.txt   |   8 +
>>   .../devicetree/bindings/soc/ti/wkup_m3_ipc.txt     |  57 +++
>>   drivers/mailbox/omap-mailbox.c                     |  49 +-
>>   drivers/soc/ti/Kconfig                             |  10 +
>>   drivers/soc/ti/Makefile                            |   1 +
>>   drivers/soc/ti/wkup_m3_ipc.c                       | 508 +++++++++++++++++++++
>>   include/linux/wkup_m3_ipc.h                        |  55 +++
>>   7 files changed, 684 insertions(+), 4 deletions(-)
>>   create mode 100644 Documentation/devicetree/bindings/soc/ti/wkup_m3_ipc.txt
>>   create mode 100644 drivers/soc/ti/wkup_m3_ipc.c
>>   create mode 100644 include/linux/wkup_m3_ipc.h
>>
>> --
>> 2.4.6
>>

  reply	other threads:[~2015-12-02 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  0:14 [PATCH v3 0/3] soc: ti: Introduce wkup_m3_ipc driver Dave Gerlach
2015-09-23  0:14 ` [PATCH v3 1/3] mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle Dave Gerlach
     [not found]   ` <1442967294-23837-2-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2015-10-21  4:44     ` Jassi Brar
2015-10-22  0:05       ` Suman Anna
2015-10-22  4:42         ` Jassi Brar
2015-10-22 16:00           ` Suman Anna
2015-09-23  0:14 ` [PATCH v3 2/3] Documentation: dt: add bindings for TI Wakeup M3 IPC device Dave Gerlach
2015-09-23  0:14 ` [PATCH v3 3/3] soc: ti: Add wkup_m3_ipc driver Dave Gerlach
     [not found] ` <1442967294-23837-1-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2015-10-20 16:18   ` [PATCH v3 0/3] soc: ti: Introduce " Tony Lindgren
2015-12-02 20:29     ` Dave Gerlach [this message]
     [not found]       ` <565F54C1.8090407-l0cyMroinI0@public.gmane.org>
2015-12-03 15:47         ` Tony Lindgren

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=565F54C1.8090407@ti.com \
    --to=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=s-anna@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).