From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
"open list:REMOTE PROCESSOR \(REMOTEPROC\) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP.
Date: Mon, 11 Nov 2019 15:10:23 -0800 [thread overview]
Message-ID: <20191111231023.GD3108315@builder> (raw)
In-Reply-To: <20191014075812.181942-4-pihsun@chromium.org>
On Mon 14 Oct 00:58 PDT 2019, Pi-Hsun Shih wrote:
> Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.
>
Hi Pi-Hsun,
Sorry for not reviewing this in a timely manner! This looks good, just
some very minor comments below.
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
[..]
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index f2e5e70a58f2..7896cefb2dc0 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -15,6 +15,7 @@
> #include <linux/platform_device.h>
> #include <linux/remoteproc.h>
> #include <linux/remoteproc/mtk_scp.h>
> +#include <linux/rpmsg/mtk_rpmsg.h>
>
> #include "mtk_common.h"
> #include "remoteproc_internal.h"
> @@ -407,6 +408,31 @@ static void scp_unmap_memory_region(struct mtk_scp *scp)
> of_reserved_mem_device_release(scp->dev);
> }
>
> +static struct mtk_rpmsg_info mtk_scp_rpmsg_info = {
> + .send_ipi = scp_ipi_send,
> + .register_ipi = scp_ipi_register,
> + .unregister_ipi = scp_ipi_unregister,
These are exported symbols, so unless you see a need to support
alternative implementations in the near future just skip the function
pointers and call them directly.
> + .ns_ipi_id = SCP_IPI_NS_SERVICE,
> +};
> +
[..]
> diff --git a/drivers/rpmsg/mtk_rpmsg.c b/drivers/rpmsg/mtk_rpmsg.c
[..]
> +static void __ept_release(struct kref *kref)
Please make this __mtk_ept_release() to make it clear that this is
not a framework function.
> +{
> + struct rpmsg_endpoint *ept = container_of(kref, struct rpmsg_endpoint,
> + refcount);
> + kfree(to_mtk_rpmsg_endpoint(ept));
> +}
> +
> +static void mtk_rpmsg_ipi_handler(void *data, unsigned int len, void *priv)
> +{
> + struct mtk_rpmsg_endpoint *mept = priv;
> + struct rpmsg_endpoint *ept = &mept->ept;
> + int ret;
> +
> + ret = (*ept->cb)(ept->rpdev, data, len, ept->priv, ept->addr);
> + if (ret)
> + dev_warn(&ept->rpdev->dev, "rpmsg handler return error = %d",
> + ret);
> +}
> +
> +static struct rpmsg_endpoint *
> +__rpmsg_create_ept(struct mtk_rpmsg_rproc_subdev *mtk_subdev,
__mtk_create_ept()
> + struct rpmsg_device *rpdev, rpmsg_rx_cb_t cb, void *priv,
> + u32 id)
> +{
Regards,
Bjorn
_______________________________________________
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: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP.
Date: Mon, 11 Nov 2019 15:10:26 -0800 [thread overview]
Message-ID: <20191111231023.GD3108315@builder> (raw)
In-Reply-To: <20191014075812.181942-4-pihsun@chromium.org>
On Mon 14 Oct 00:58 PDT 2019, Pi-Hsun Shih wrote:
> Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.
>
Hi Pi-Hsun,
Sorry for not reviewing this in a timely manner! This looks good, just
some very minor comments below.
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
[..]
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index f2e5e70a58f2..7896cefb2dc0 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -15,6 +15,7 @@
> #include <linux/platform_device.h>
> #include <linux/remoteproc.h>
> #include <linux/remoteproc/mtk_scp.h>
> +#include <linux/rpmsg/mtk_rpmsg.h>
>
> #include "mtk_common.h"
> #include "remoteproc_internal.h"
> @@ -407,6 +408,31 @@ static void scp_unmap_memory_region(struct mtk_scp *scp)
> of_reserved_mem_device_release(scp->dev);
> }
>
> +static struct mtk_rpmsg_info mtk_scp_rpmsg_info = {
> + .send_ipi = scp_ipi_send,
> + .register_ipi = scp_ipi_register,
> + .unregister_ipi = scp_ipi_unregister,
These are exported symbols, so unless you see a need to support
alternative implementations in the near future just skip the function
pointers and call them directly.
> + .ns_ipi_id = SCP_IPI_NS_SERVICE,
> +};
> +
[..]
> diff --git a/drivers/rpmsg/mtk_rpmsg.c b/drivers/rpmsg/mtk_rpmsg.c
[..]
> +static void __ept_release(struct kref *kref)
Please make this __mtk_ept_release() to make it clear that this is
not a framework function.
> +{
> + struct rpmsg_endpoint *ept = container_of(kref, struct rpmsg_endpoint,
> + refcount);
> + kfree(to_mtk_rpmsg_endpoint(ept));
> +}
> +
> +static void mtk_rpmsg_ipi_handler(void *data, unsigned int len, void *priv)
> +{
> + struct mtk_rpmsg_endpoint *mept = priv;
> + struct rpmsg_endpoint *ept = &mept->ept;
> + int ret;
> +
> + ret = (*ept->cb)(ept->rpdev, data, len, ept->priv, ept->addr);
> + if (ret)
> + dev_warn(&ept->rpdev->dev, "rpmsg handler return error = %d",
> + ret);
> +}
> +
> +static struct rpmsg_endpoint *
> +__rpmsg_create_ept(struct mtk_rpmsg_rproc_subdev *mtk_subdev,
__mtk_create_ept()
> + struct rpmsg_device *rpdev, rpmsg_rx_cb_t cb, void *priv,
> + u32 id)
> +{
Regards,
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
"open list:REMOTE PROCESSOR \(REMOTEPROC\) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP.
Date: Mon, 11 Nov 2019 15:10:23 -0800 [thread overview]
Message-ID: <20191111231023.GD3108315@builder> (raw)
In-Reply-To: <20191014075812.181942-4-pihsun@chromium.org>
On Mon 14 Oct 00:58 PDT 2019, Pi-Hsun Shih wrote:
> Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.
>
Hi Pi-Hsun,
Sorry for not reviewing this in a timely manner! This looks good, just
some very minor comments below.
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
[..]
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index f2e5e70a58f2..7896cefb2dc0 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -15,6 +15,7 @@
> #include <linux/platform_device.h>
> #include <linux/remoteproc.h>
> #include <linux/remoteproc/mtk_scp.h>
> +#include <linux/rpmsg/mtk_rpmsg.h>
>
> #include "mtk_common.h"
> #include "remoteproc_internal.h"
> @@ -407,6 +408,31 @@ static void scp_unmap_memory_region(struct mtk_scp *scp)
> of_reserved_mem_device_release(scp->dev);
> }
>
> +static struct mtk_rpmsg_info mtk_scp_rpmsg_info = {
> + .send_ipi = scp_ipi_send,
> + .register_ipi = scp_ipi_register,
> + .unregister_ipi = scp_ipi_unregister,
These are exported symbols, so unless you see a need to support
alternative implementations in the near future just skip the function
pointers and call them directly.
> + .ns_ipi_id = SCP_IPI_NS_SERVICE,
> +};
> +
[..]
> diff --git a/drivers/rpmsg/mtk_rpmsg.c b/drivers/rpmsg/mtk_rpmsg.c
[..]
> +static void __ept_release(struct kref *kref)
Please make this __mtk_ept_release() to make it clear that this is
not a framework function.
> +{
> + struct rpmsg_endpoint *ept = container_of(kref, struct rpmsg_endpoint,
> + refcount);
> + kfree(to_mtk_rpmsg_endpoint(ept));
> +}
> +
> +static void mtk_rpmsg_ipi_handler(void *data, unsigned int len, void *priv)
> +{
> + struct mtk_rpmsg_endpoint *mept = priv;
> + struct rpmsg_endpoint *ept = &mept->ept;
> + int ret;
> +
> + ret = (*ept->cb)(ept->rpdev, data, len, ept->priv, ept->addr);
> + if (ret)
> + dev_warn(&ept->rpdev->dev, "rpmsg handler return error = %d",
> + ret);
> +}
> +
> +static struct rpmsg_endpoint *
> +__rpmsg_create_ept(struct mtk_rpmsg_rproc_subdev *mtk_subdev,
__mtk_create_ept()
> + struct rpmsg_device *rpdev, rpmsg_rx_cb_t cb, void *priv,
> + u32 id)
> +{
Regards,
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP.
Date: Mon, 11 Nov 2019 15:10:23 -0800 [thread overview]
Message-ID: <20191111231023.GD3108315@builder> (raw)
In-Reply-To: <20191014075812.181942-4-pihsun@chromium.org>
On Mon 14 Oct 00:58 PDT 2019, Pi-Hsun Shih wrote:
> Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.
>
Hi Pi-Hsun,
Sorry for not reviewing this in a timely manner! This looks good, just
some very minor comments below.
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
[..]
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index f2e5e70a58f2..7896cefb2dc0 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -15,6 +15,7 @@
> #include <linux/platform_device.h>
> #include <linux/remoteproc.h>
> #include <linux/remoteproc/mtk_scp.h>
> +#include <linux/rpmsg/mtk_rpmsg.h>
>
> #include "mtk_common.h"
> #include "remoteproc_internal.h"
> @@ -407,6 +408,31 @@ static void scp_unmap_memory_region(struct mtk_scp *scp)
> of_reserved_mem_device_release(scp->dev);
> }
>
> +static struct mtk_rpmsg_info mtk_scp_rpmsg_info = {
> + .send_ipi = scp_ipi_send,
> + .register_ipi = scp_ipi_register,
> + .unregister_ipi = scp_ipi_unregister,
These are exported symbols, so unless you see a need to support
alternative implementations in the near future just skip the function
pointers and call them directly.
> + .ns_ipi_id = SCP_IPI_NS_SERVICE,
> +};
> +
[..]
> diff --git a/drivers/rpmsg/mtk_rpmsg.c b/drivers/rpmsg/mtk_rpmsg.c
[..]
> +static void __ept_release(struct kref *kref)
Please make this __mtk_ept_release() to make it clear that this is
not a framework function.
> +{
> + struct rpmsg_endpoint *ept = container_of(kref, struct rpmsg_endpoint,
> + refcount);
> + kfree(to_mtk_rpmsg_endpoint(ept));
> +}
> +
> +static void mtk_rpmsg_ipi_handler(void *data, unsigned int len, void *priv)
> +{
> + struct mtk_rpmsg_endpoint *mept = priv;
> + struct rpmsg_endpoint *ept = &mept->ept;
> + int ret;
> +
> + ret = (*ept->cb)(ept->rpdev, data, len, ept->priv, ept->addr);
> + if (ret)
> + dev_warn(&ept->rpdev->dev, "rpmsg handler return error = %d",
> + ret);
> +}
> +
> +static struct rpmsg_endpoint *
> +__rpmsg_create_ept(struct mtk_rpmsg_rproc_subdev *mtk_subdev,
__mtk_create_ept()
> + struct rpmsg_device *rpdev, rpmsg_rx_cb_t cb, void *priv,
> + u32 id)
> +{
Regards,
Bjorn
next prev parent reply other threads:[~2019-11-11 23:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 7:58 [PATCH v20 0/4] Add support for mt8183 SCP Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` [PATCH v20 1/4] dt-bindings: Add a binding for Mediatek SCP Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` [PATCH v20 2/4] remoteproc/mediatek: add SCP support for mt8183 Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-11-11 22:53 ` Bjorn Andersson
2019-11-11 22:53 ` Bjorn Andersson
2019-11-11 22:53 ` Bjorn Andersson
2019-11-11 22:53 ` Bjorn Andersson
2019-11-12 7:55 ` Pi-Hsun Shih
2019-11-12 7:55 ` Pi-Hsun Shih
2019-11-12 7:55 ` Pi-Hsun Shih
2019-10-14 7:58 ` [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-11-11 23:10 ` Bjorn Andersson [this message]
2019-11-11 23:10 ` Bjorn Andersson
2019-11-11 23:10 ` Bjorn Andersson
2019-11-11 23:10 ` Bjorn Andersson
2019-11-12 6:42 ` Pi-Hsun Shih
2019-11-12 6:42 ` Pi-Hsun Shih
2019-11-12 6:42 ` Pi-Hsun Shih
2019-11-12 7:08 ` Bjorn Andersson
2019-11-12 7:08 ` Bjorn Andersson
2019-11-12 7:08 ` Bjorn Andersson
2019-11-12 7:08 ` Bjorn Andersson
2019-10-14 7:58 ` [PATCH v20 4/4] arm64: dts: mt8183: add scp node Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
2019-10-14 7:58 ` Pi-Hsun Shih
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=20191111231023.GD3108315@builder \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ohad@wizery.com \
--cc=pihsun@chromium.org \
/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.