From: Martyn Welch <martyn.welch@collabora.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hari Nagalla <hnagalla@ti.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3 2/3] remoteproc: k4: Split out functions common with M4 driver
Date: Fri, 10 Mar 2023 13:55:03 +0000 [thread overview]
Message-ID: <0b5ea25e40cad98b2a4f7b098dfa837fcc49e478.camel@collabora.com> (raw)
In-Reply-To: <0d756429-13a5-f894-cf7d-b6f0f04da92c@collabora.com>
On Fri, 2023-03-10 at 10:53 +0100, AngeloGioacchino Del Regno wrote:
> Il 10/03/23 10:46, Martyn Welch ha scritto:
> > On Thu, 2023-03-09 at 12:04 -0600, Hari Nagalla wrote:
> > > On 3/2/23 11:14, Martyn Welch wrote:
> > > > + * @ti_sci_id: TI-SCI device identifier
> > > > + * @mbox: mailbox channel handle
> > > > + * @client: mailbox client to request the mailbox channel
> > > > + * @ipc_only: flag to indicate IPC-only mode
> > > > + */
> > > > +struct k3_rproc {
> > > > + struct device *dev;
> > > > + struct rproc *rproc;
> > > > + struct k3_rproc_mem *mem;
> > > > + int num_mems;
> > > > + struct k3_rproc_mem *rmem;
> > > > + int num_rmems;
> > > > + struct reset_control *reset;
> > > > + const struct k3_rproc_dev_data *data;
> > > > + struct ti_sci_proc *tsp;
> > > > + const struct ti_sci_handle *ti_sci;
> > > > + u32 ti_sci_id;
> > > > + struct mbox_chan *mbox;
> > > > + struct mbox_client client;
> > > > +};
> > > > +
> > > "ipc_only" mode element is missing in the structure.
> >
> > That's added with the M4F driver in the next patch - it's not part
> > of
> > the structure in the DSP driver.
>
> Martyn, I get that it's added later, but the point here is that you
> are
> documenting something that is missing! :-)
>
> You should add the kerneldoc for @ipc_only: xxxx when you actually
> introduce
> the new element... otherwise, this commit alone would trigger a
> kerneldoc warning.
>
Ah! Thanks. I'd missed that I'd left the comment in there. Yep, that
needs to be added in the next patch rather than here... :-)
Martyn
> Cheers,
> Angelo
next prev parent reply other threads:[~2023-03-10 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 17:14 [PATCH v3 0/3] TI K3 M4F support on AM64x and AM62x SoCs Martyn Welch
2023-03-02 17:14 ` [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs Martyn Welch
2023-03-03 8:06 ` Krzysztof Kozlowski
2023-03-07 18:26 ` Martyn Welch
2023-03-08 8:41 ` Krzysztof Kozlowski
2023-03-08 20:58 ` Mathieu Poirier
2023-03-09 23:18 ` Hari Nagalla
2023-03-10 15:41 ` Mathieu Poirier
2023-03-24 10:31 ` Martyn Welch
2023-03-24 12:01 ` Martyn Welch
2023-03-02 17:14 ` [PATCH v3 2/3] remoteproc: k4: Split out functions common with M4 driver Martyn Welch
2023-03-08 21:45 ` Mathieu Poirier
2023-03-09 18:04 ` Hari Nagalla
2023-03-10 9:46 ` Martyn Welch
2023-03-10 9:53 ` AngeloGioacchino Del Regno
2023-03-10 13:55 ` Martyn Welch [this message]
2023-03-02 17:14 ` [PATCH v3 3/3] remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem Martyn Welch
2023-03-09 23:01 ` Mathieu Poirier
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=0b5ea25e40cad98b2a4f7b098dfa837fcc49e478.camel@collabora.com \
--to=martyn.welch@collabora.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hnagalla@ti.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=p.zabel@pengutronix.de \
/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