[GIT,PULL] New Mailbox framework for 3.18

Message ID CAJe_Zhf73TXxAjBq_cCJB_oBC1Ff_ErN7TP4HsO-_BzhiPZkGQ@mail.gmail.com
State New
Headers show

Pull-request

git://git.linaro.org/landing-teams/working/fujitsu/integration.git

Message

Jassi Brar Oct. 8, 2014, 5:39 a.m.
Hi Linus,

A framework for Mailbox controllers and clients have been cooking for
more than a year now. Everybody in the CC list had been copied on
patchset revisions and most of them have made sounds of approval,
though just one concrete Reviewed-by. The patchset has also been in
linux-next for a couple of weeks now and no conflict has been
reported. The framework has the backing of at least 5 platforms,
though I can't say if/when they upstream their drivers (some
businesses have 'changed').


The following changes since commit 9a50aaefc1b896e734bf7faf3d085f71a360ce97:

  Merge tag 'scsi-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2014-10-07
21:29:18 -0400)

are available in the git repository at:


  git://git.linaro.org/landing-teams/working/fujitsu/integration.git
mailbox-for-linus

for you to fetch changes up to 9f3e3cacb2ffdefe28c7cf490bf543e4dcb2770a:

  dt: mailbox: add generic bindings (2014-10-08 10:39:42 +0530)

----------------------------------------------------------------
Jassi Brar (3):
      mailbox: Introduce framework for mailbox
      doc: add documentation for mailbox framework
      dt: mailbox: add generic bindings

Suman Anna (1):
      mailbox: rename pl320-ipc specific mailbox.h

 .../devicetree/bindings/mailbox/mailbox.txt        |  38 ++
 Documentation/mailbox.txt                          | 122 ++++++
 MAINTAINERS                                        |   8 +
 arch/arm/mach-highbank/highbank.c                  |   2 +-
 drivers/cpufreq/highbank-cpufreq.c                 |   2 +-
 drivers/mailbox/Makefile                           |   4 +
 drivers/mailbox/mailbox.c                          | 465 +++++++++++++++++++++
 drivers/mailbox/pl320-ipc.c                        |   2 +-
 include/linux/mailbox_client.h                     |  46 ++
 include/linux/mailbox_controller.h                 | 133 ++++++
 include/linux/{mailbox.h => pl320-ipc.h}           |   0
 11 files changed, 819 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/mailbox/mailbox.txt
 create mode 100644 Documentation/mailbox.txt
 create mode 100644 drivers/mailbox/mailbox.c
 create mode 100644 include/linux/mailbox_client.h
 create mode 100644 include/linux/mailbox_controller.h
 rename include/linux/{mailbox.h => pl320-ipc.h} (100%)

Comments

Suman Anna Oct. 8, 2014, 11:23 p.m. | #1
On 10/08/2014 12:39 AM, Jassi Brar wrote:
> Hi Linus,
> 
> A framework for Mailbox controllers and clients have been cooking for
> more than a year now. Everybody in the CC list had been copied on
> patchset revisions and most of them have made sounds of approval,
> though just one concrete Reviewed-by. The patchset has also been in
> linux-next for a couple of weeks now and no conflict has been
> reported. The framework has the backing of at least 5 platforms,
> though I can't say if/when they upstream their drivers (some
> businesses have 'changed').

Thanks Jassi. OMAP is ready, and because of merge order dependencies is
held back. We should be able to have the framework adaptation merged on
the next kernel version once this is in.

regards
Suman

> 
> 
> The following changes since commit 9a50aaefc1b896e734bf7faf3d085f71a360ce97:
> 
>   Merge tag 'scsi-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2014-10-07
> 21:29:18 -0400)
> 
> are available in the git repository at:
> 
> 
>   git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> mailbox-for-linus
> 
> for you to fetch changes up to 9f3e3cacb2ffdefe28c7cf490bf543e4dcb2770a:
> 
>   dt: mailbox: add generic bindings (2014-10-08 10:39:42 +0530)
> 
> ----------------------------------------------------------------
> Jassi Brar (3):
>       mailbox: Introduce framework for mailbox
>       doc: add documentation for mailbox framework
>       dt: mailbox: add generic bindings
> 
> Suman Anna (1):
>       mailbox: rename pl320-ipc specific mailbox.h
> 
>  .../devicetree/bindings/mailbox/mailbox.txt        |  38 ++
>  Documentation/mailbox.txt                          | 122 ++++++
>  MAINTAINERS                                        |   8 +
>  arch/arm/mach-highbank/highbank.c                  |   2 +-
>  drivers/cpufreq/highbank-cpufreq.c                 |   2 +-
>  drivers/mailbox/Makefile                           |   4 +
>  drivers/mailbox/mailbox.c                          | 465 +++++++++++++++++++++
>  drivers/mailbox/pl320-ipc.c                        |   2 +-
>  include/linux/mailbox_client.h                     |  46 ++
>  include/linux/mailbox_controller.h                 | 133 ++++++
>  include/linux/{mailbox.h => pl320-ipc.h}           |   0
>  11 files changed, 819 insertions(+), 3 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/mailbox/mailbox.txt
>  create mode 100644 Documentation/mailbox.txt
>  create mode 100644 drivers/mailbox/mailbox.c
>  create mode 100644 include/linux/mailbox_client.h
>  create mode 100644 include/linux/mailbox_controller.h
>  rename include/linux/{mailbox.h => pl320-ipc.h} (100%)
> 
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Jassi Brar Oct. 20, 2014, 9:53 a.m. | #2
On 8 October 2014 11:09, Jassi Brar <jaswinder.singh@linaro.org> wrote:
> Hi Linus,
>
> A framework for Mailbox controllers and clients have been cooking for
> more than a year now. Everybody in the CC list had been copied on
> patchset revisions and most of them have made sounds of approval,
> though just one concrete Reviewed-by. The patchset has also been in
> linux-next for a couple of weeks now and no conflict has been
> reported. The framework has the backing of at least 5 platforms,
> though I can't say if/when they upstream their drivers (some
> businesses have 'changed').
>
>
> The following changes since commit 9a50aaefc1b896e734bf7faf3d085f71a360ce97:
>
>   Merge tag 'scsi-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2014-10-07
> 21:29:18 -0400)
>
> are available in the git repository at:
>
>
>   git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> mailbox-for-linus
>
> for you to fetch changes up to 9f3e3cacb2ffdefe28c7cf490bf543e4dcb2770a:
>
>   dt: mailbox: add generic bindings (2014-10-08 10:39:42 +0530)
>
> ----------------------------------------------------------------
> Jassi Brar (3):
>       mailbox: Introduce framework for mailbox
>       doc: add documentation for mailbox framework
>       dt: mailbox: add generic bindings
>
> Suman Anna (1):
>       mailbox: rename pl320-ipc specific mailbox.h
>
>  .../devicetree/bindings/mailbox/mailbox.txt        |  38 ++
>  Documentation/mailbox.txt                          | 122 ++++++
>  MAINTAINERS                                        |   8 +
>  arch/arm/mach-highbank/highbank.c                  |   2 +-
>  drivers/cpufreq/highbank-cpufreq.c                 |   2 +-
>  drivers/mailbox/Makefile                           |   4 +
>  drivers/mailbox/mailbox.c                          | 465 +++++++++++++++++++++
>  drivers/mailbox/pl320-ipc.c                        |   2 +-
>  include/linux/mailbox_client.h                     |  46 ++
>  include/linux/mailbox_controller.h                 | 133 ++++++
>  include/linux/{mailbox.h => pl320-ipc.h}           |   0
>  11 files changed, 819 insertions(+), 3 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/mailbox/mailbox.txt
>  create mode 100644 Documentation/mailbox.txt
>  create mode 100644 drivers/mailbox/mailbox.c
>  create mode 100644 include/linux/mailbox_client.h
>  create mode 100644 include/linux/mailbox_controller.h
>  rename include/linux/{mailbox.h => pl320-ipc.h} (100%)
>
Hi Linus,
  While I was speculating on the reasons why you were not merging the
patchset - not enough Acked-Bys, you want it via asoc, my git server
down (I am not aware) or you just forgot in the unlikely case - I
missed the window.
 There are couple of platforms waiting for the api to get upstream and
now I have the devs on my back. Assuming I messed up the pull request
somehow, may I know how?

Thanks
-Jassi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Arnd Bergmann Oct. 21, 2014, 7:43 a.m. | #3
On Monday 20 October 2014 15:23:38 Jassi Brar wrote:
> On 8 October 2014 11:09, Jassi Brar <jaswinder.singh@linaro.org> wrote:
> > Hi Linus,
> >
> > A framework for Mailbox controllers and clients have been cooking for
> > more than a year now. Everybody in the CC list had been copied on
> > patchset revisions and most of them have made sounds of approval,
> > though just one concrete Reviewed-by. The patchset has also been in
> > linux-next for a couple of weeks now and no conflict has been
> > reported. The framework has the backing of at least 5 platforms,
> > though I can't say if/when they upstream their drivers (some
> > businesses have 'changed').
> >
> Hi Linus,
>   While I was speculating on the reasons why you were not merging the
> patchset - not enough Acked-Bys, you want it via asoc, my git server
> down (I am not aware) or you just forgot in the unlikely case - I
> missed the window.
>  There are couple of platforms waiting for the api to get upstream and
> now I have the devs on my back. Assuming I messed up the pull request
> somehow, may I know how?

Jassi,

I assume a contributing factor here was that you rebased the tree
just before submission, which is always a bad sign.

There is a small chance that Linus will still pull this for v3.18, as he
said that he'd take a few things that have been submitted in time. If
not, please rebase once more on top of v3.18-rc1 and send a pull request
to arm@kernel.org so we can put it into arm-soc for 3.19.

Linus, 

I think it would be good to have it, I had an earlier version in arm-soc
a couple of merge windows ago but ended up not submitting it back then
because of a last-minute problem. All issues have been resolved since, 
and we have a number of platforms that want to add drivers on top of
the framework.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Jassi Brar Oct. 21, 2014, 9:10 a.m. | #4
On 21 October 2014 13:13, Arnd Bergmann <arnd@arndb.de> wrote:
> On Monday 20 October 2014 15:23:38 Jassi Brar wrote:
>> On 8 October 2014 11:09, Jassi Brar <jaswinder.singh@linaro.org> wrote:
>> > Hi Linus,
>> >
>> > A framework for Mailbox controllers and clients have been cooking for
>> > more than a year now. Everybody in the CC list had been copied on
>> > patchset revisions and most of them have made sounds of approval,
>> > though just one concrete Reviewed-by. The patchset has also been in
>> > linux-next for a couple of weeks now and no conflict has been
>> > reported. The framework has the backing of at least 5 platforms,
>> > though I can't say if/when they upstream their drivers (some
>> > businesses have 'changed').
>> >
>> Hi Linus,
>>   While I was speculating on the reasons why you were not merging the
>> patchset - not enough Acked-Bys, you want it via asoc, my git server
>> down (I am not aware) or you just forgot in the unlikely case - I
>> missed the window.
>>  There are couple of platforms waiting for the api to get upstream and
>> now I have the devs on my back. Assuming I messed up the pull request
>> somehow, may I know how?
>
> Jassi,
>
> I assume a contributing factor here was that you rebased the tree
> just before submission, which is always a bad sign.
>
> There is a small chance that Linus will still pull this for v3.18, as he
> said that he'd take a few things that have been submitted in time. If
> not, please rebase once more on top of v3.18-rc1 and send a pull request
> to arm@kernel.org so we can put it into arm-soc for 3.19.
>
OK, I will. And thanks for pointing out the issue with rebasing.

Thanks
Jassi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Suman Anna Oct. 21, 2014, 4:25 p.m. | #5
Hi,

On 10/21/2014 02:43 AM, Arnd Bergmann wrote:
> On Monday 20 October 2014 15:23:38 Jassi Brar wrote:
>> On 8 October 2014 11:09, Jassi Brar <jaswinder.singh@linaro.org> wrote:
>>> Hi Linus,
>>>
>>> A framework for Mailbox controllers and clients have been cooking for
>>> more than a year now. Everybody in the CC list had been copied on
>>> patchset revisions and most of them have made sounds of approval,
>>> though just one concrete Reviewed-by. The patchset has also been in
>>> linux-next for a couple of weeks now and no conflict has been
>>> reported. The framework has the backing of at least 5 platforms,
>>> though I can't say if/when they upstream their drivers (some
>>> businesses have 'changed').
>>>
>> Hi Linus,
>>   While I was speculating on the reasons why you were not merging the
>> patchset - not enough Acked-Bys, you want it via asoc, my git server
>> down (I am not aware) or you just forgot in the unlikely case - I
>> missed the window.
>>  There are couple of platforms waiting for the api to get upstream and
>> now I have the devs on my back. Assuming I messed up the pull request
>> somehow, may I know how?
> 
> Jassi,
> 
> I assume a contributing factor here was that you rebased the tree
> just before submission, which is always a bad sign.
> 
> There is a small chance that Linus will still pull this for v3.18, as he
> said that he'd take a few things that have been submitted in time. If
> not, please rebase once more on top of v3.18-rc1 and send a pull request
> to arm@kernel.org so we can put it into arm-soc for 3.19.
> 
> Linus, 
> 
> I think it would be good to have it, I had an earlier version in arm-soc
> a couple of merge windows ago but ended up not submitting it back then
> because of a last-minute problem. All issues have been resolved since, 
> and we have a number of platforms that want to add drivers on top of
> the framework.

In terms of users, the OMAP mailbox adaptation patches to this framework
is ready [1], and this is one of the main dependencies to achieve PM
suspend/resume on the TI AM335/AM437 SoCs. I would have to rebase the
patches onto the appropriate -rc with the framework patches in, as the
remaining mailbox dependencies did make it into 3.18-rc1. I was
initially hoping that this would be 3.18-rc1, and the OMAP patches to
make it into 3.19, but if this is going to be 3.19, then the OMAP
adaptation can be baselined off an immutable mailbox framework branch,
and come through the arm-soc tree as well.

[1] http://marc.info/?l=linux-omap&m=141038447817775&w=2

regards
Suman

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Linus Torvalds Oct. 21, 2014, 6:20 p.m. | #6
On Mon, Oct 20, 2014 at 2:53 AM, Jassi Brar <jaswinder.singh@linaro.org> wrote:
> Hi Linus,
>   While I was speculating on the reasons why you were not merging the
> patchset - not enough Acked-Bys, you want it via asoc, my git server
> down (I am not aware) or you just forgot in the unlikely case - I
> missed the window.

It's good that you just resent. I wanted to get more feedback on the
patches, but due to travels what ended up happening was that I just
forgot about it instead.

There's been enough acks in this thread that I'll just pull it.

                   Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/