All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bibby Hsieh <bibby.hsieh@mediatek.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, CK HU <ck.hu@mediatek.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<srv_heupstream@mediatek.com>,
	Nicolas Boichat <drinkcat@chromium.org>,
	Dennis-YC Hsieh <dennis-yc.hsieh@mediatek.com>,
	Houlong Wei <houlong.wei@mediatek.com>,
	Bibby Hsieh <bibby.hsieh@mediatek.com>
Subject: [PATCH v1 0/3] Remove atomic_exec
Date: Mon, 17 Feb 2020 17:05:29 +0800	[thread overview]
Message-ID: <20200217090532.16019-1-bibby.hsieh@mediatek.com> (raw)

The atomic_exec was designed for processing continuous
packets of commands in atomic way for Mediatek DRM driver.

After we implement flush function, Mediatek DRM driver
doesn't need atomic_exec, the primary concept is to let
Mediatek DRM driver can make sure previous message done or
be aborted (if the message has not started yet) before they
send next message.

Changes since v0:
 - move the binding changes to first
 - remove unnecessary changes

Bibby Hsieh (3):
  dt-binding: gce: remove atomic_exec in mboxes property
  mailbox: mediatek: implement flush function
  mailbox: mediatek: remove implementation related to atomic_exec

 .../devicetree/bindings/mailbox/mtk-gce.txt   |  10 +-
 drivers/mailbox/mtk-cmdq-mailbox.c            | 128 ++++++++----------
 2 files changed, 64 insertions(+), 74 deletions(-)

-- 
2.18.0

WARNING: multiple messages have this Message-ID (diff)
From: Bibby Hsieh <bibby.hsieh@mediatek.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, CK HU <ck.hu@mediatek.com>
Cc: devicetree@vger.kernel.org,
	Nicolas Boichat <drinkcat@chromium.org>,
	srv_heupstream@mediatek.com, linux-kernel@vger.kernel.org,
	Houlong Wei <houlong.wei@mediatek.com>,
	Dennis-YC Hsieh <dennis-yc.hsieh@mediatek.com>,
	linux-mediatek@lists.infradead.org,
	Bibby Hsieh <bibby.hsieh@mediatek.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/3] Remove atomic_exec
Date: Mon, 17 Feb 2020 17:05:29 +0800	[thread overview]
Message-ID: <20200217090532.16019-1-bibby.hsieh@mediatek.com> (raw)

The atomic_exec was designed for processing continuous
packets of commands in atomic way for Mediatek DRM driver.

After we implement flush function, Mediatek DRM driver
doesn't need atomic_exec, the primary concept is to let
Mediatek DRM driver can make sure previous message done or
be aborted (if the message has not started yet) before they
send next message.

Changes since v0:
 - move the binding changes to first
 - remove unnecessary changes

Bibby Hsieh (3):
  dt-binding: gce: remove atomic_exec in mboxes property
  mailbox: mediatek: implement flush function
  mailbox: mediatek: remove implementation related to atomic_exec

 .../devicetree/bindings/mailbox/mtk-gce.txt   |  10 +-
 drivers/mailbox/mtk-cmdq-mailbox.c            | 128 ++++++++----------
 2 files changed, 64 insertions(+), 74 deletions(-)

-- 
2.18.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Bibby Hsieh <bibby.hsieh@mediatek.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, CK HU <ck.hu@mediatek.com>
Cc: devicetree@vger.kernel.org,
	Nicolas Boichat <drinkcat@chromium.org>,
	srv_heupstream@mediatek.com, linux-kernel@vger.kernel.org,
	Houlong Wei <houlong.wei@mediatek.com>,
	Dennis-YC Hsieh <dennis-yc.hsieh@mediatek.com>,
	linux-mediatek@lists.infradead.org,
	Bibby Hsieh <bibby.hsieh@mediatek.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/3] Remove atomic_exec
Date: Mon, 17 Feb 2020 17:05:29 +0800	[thread overview]
Message-ID: <20200217090532.16019-1-bibby.hsieh@mediatek.com> (raw)

The atomic_exec was designed for processing continuous
packets of commands in atomic way for Mediatek DRM driver.

After we implement flush function, Mediatek DRM driver
doesn't need atomic_exec, the primary concept is to let
Mediatek DRM driver can make sure previous message done or
be aborted (if the message has not started yet) before they
send next message.

Changes since v0:
 - move the binding changes to first
 - remove unnecessary changes

Bibby Hsieh (3):
  dt-binding: gce: remove atomic_exec in mboxes property
  mailbox: mediatek: implement flush function
  mailbox: mediatek: remove implementation related to atomic_exec

 .../devicetree/bindings/mailbox/mtk-gce.txt   |  10 +-
 drivers/mailbox/mtk-cmdq-mailbox.c            | 128 ++++++++----------
 2 files changed, 64 insertions(+), 74 deletions(-)

-- 
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-02-17  9:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  9:05 Bibby Hsieh [this message]
2020-02-17  9:05 ` [PATCH v1 0/3] Remove atomic_exec Bibby Hsieh
2020-02-17  9:05 ` Bibby Hsieh
2020-02-17  9:05 ` [PATCH v1 1/3] dt-binding: gce: remove atomic_exec in mboxes property Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh
2020-02-26 15:18   ` Rob Herring
2020-02-26 15:18     ` Rob Herring
2020-02-26 15:18     ` Rob Herring
2020-02-17  9:05 ` [PATCH v1 2/3] mailbox: mediatek: implement flush function Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh
2020-02-17  9:29   ` CK Hu
2020-02-17  9:29     ` CK Hu
2020-02-17  9:29     ` CK Hu
2020-03-06  3:55     ` Bibby Hsieh
2020-03-06  3:55       ` Bibby Hsieh
2020-03-06  3:55       ` Bibby Hsieh
2020-02-17  9:05 ` [PATCH v1 3/3] mailbox: mediatek: remove implementation related to atomic_exec Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh
2020-02-17  9:05   ` Bibby Hsieh

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=20200217090532.16019-1-bibby.hsieh@mediatek.com \
    --to=bibby.hsieh@mediatek.com \
    --cc=ck.hu@mediatek.com \
    --cc=dennis-yc.hsieh@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=houlong.wei@mediatek.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=srv_heupstream@mediatek.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.