From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Hari Nagalla <hnagalla@ti.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
p.zabel@pengutronix.de, martyn.welch@collabora.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/4] remoteproc: k3: Split out data structures common with M4 driver
Date: Wed, 13 Sep 2023 13:34:01 +0200 [thread overview]
Message-ID: <32e308fa-1118-e17a-8038-c28cb2484c92@linaro.org> (raw)
In-Reply-To: <20230913111644.29889-3-hnagalla@ti.com>
On 13/09/2023 13:16, Hari Nagalla wrote:
> From: Martyn Welch <martyn.welch@collabora.com>
>
> We will be adding the M4F driver which shares a lot of commonality
> with the DSP driver. Common data structures are introduced here.
>
> Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> ---
> Changes in v6:
> - Created a separate patch for data structures to ease review
>
> drivers/remoteproc/ti_k3_common.h | 103 ++++++++++++++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 drivers/remoteproc/ti_k3_common.h
>
> diff --git a/drivers/remoteproc/ti_k3_common.h b/drivers/remoteproc/ti_k3_common.h
> new file mode 100644
> index 000000000000..5e1f27741183
> --- /dev/null
> +++ b/drivers/remoteproc/ti_k3_common.h
> @@ -0,0 +1,103 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +/*
> + * TI K3 Remote Processor(s) driver common code
> + *
> + * Refactored from ti_k3_dsp_remoteproc.c.
> + *
> + * ti_k3_dsp_remoteproc.c:
> + * Copyright (C) 2018-2022 Texas Instruments Incorporated - https://www.ti.com/
> + * Suman Anna <s-anna@ti.com>
> + */
> +
> +#ifndef REMOTEPROC_TI_K3_COMMON_H
> +#define REMOTEPROC_TI_K3_COMMON_H
> +
> +#define KEYSTONE_RPROC_LOCAL_ADDRESS_MASK (SZ_16M - 1)
> +
> +/**
> + * struct k3_rproc_mem - internal memory structure
> + * @cpu_addr: MPU virtual address of the memory region
> + * @bus_addr: Bus address used to access the memory region
> + * @dev_addr: Device address of the memory region from DSP view
> + * @size: Size of the memory region
> + */
> +struct k3_rproc_mem {
> + void __iomem *cpu_addr;
> + phys_addr_t bus_addr;
> + u32 dev_addr;
> + size_t size;
Where is the split? I see only addition here.
Where is the usage of this header? This is basically dead code. Don't
add dead code, but instead actually move the structures here! Move is
cut and paste, not just paste.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-13 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 11:16 [PATCH v6 0/4] TI K3 M4F support on AM64x and AM62x SoCs Hari Nagalla
2023-09-13 11:16 ` [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Hari Nagalla
2023-09-13 11:32 ` Krzysztof Kozlowski
2023-09-13 13:59 ` Hari Nagalla
2023-09-13 15:43 ` Krzysztof Kozlowski
2023-09-13 12:36 ` Rob Herring
2023-09-13 15:54 ` Krzysztof Kozlowski
2023-09-14 15:35 ` Rob Herring
2023-09-13 11:16 ` [PATCH v6 2/4] remoteproc: k3: Split out data structures common with M4 driver Hari Nagalla
2023-09-13 11:34 ` Krzysztof Kozlowski [this message]
2023-09-13 11:16 ` [PATCH v6 3/4] remoteproc: k3: Split out functions " Hari Nagalla
2023-09-13 11:37 ` Krzysztof Kozlowski
2023-09-13 11:16 ` [PATCH v6 4/4] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Hari Nagalla
2023-09-13 11:34 ` Krzysztof Kozlowski
2023-09-13 11:36 ` Krzysztof Kozlowski
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=32e308fa-1118-e17a-8038-c28cb2484c92@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.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 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).