From: Dan Carpenter <dan.carpenter@linaro.org>
To: Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
Cc: gregkh@linuxfoundation.org, ovidiu.panait.oss@gmail.com,
gshahrouzi@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] staging: axis-fifo: refactor device tree parsing
Date: Mon, 2 Feb 2026 11:32:08 +0300 [thread overview]
Message-ID: <aYBhCBMkxb-TlVFH@stanley.mountain> (raw)
In-Reply-To: <20260131182732.62857-3-gustavopiazdasilva2102@gmail.com>
On Sat, Jan 31, 2026 at 03:27:32PM -0300, Gustavo Piaz da Silva wrote:
> Refactor the device tree parsing logic in axis_fifo_probe() to reduce
>
> code duplication and improve readability.
>
> Create a helper function axis_fifo_get_u32() to handle property reading
>
> and error checking, replacing repetitive of_property_read_u32() calls.
>
> This eliminates the goto logic for error handling in the probe path and
>
> consolidates error logging.
>
Delete the extra blank lines.
> Signed-off-by: Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
> ---
No changelog explaining what changed vs v2.
> drivers/staging/axis-fifo/axis-fifo.c | 76 +++++++++------------------
> 1 file changed, 25 insertions(+), 51 deletions(-)
>
> diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
> index 7bc7bf191250..1e3059ec4fbd 100644
> --- a/drivers/staging/axis-fifo/axis-fifo.c
> +++ b/drivers/staging/axis-fifo/axis-fifo.c
> @@ -482,68 +482,42 @@ static void axis_fifo_debugfs_init(struct axis_fifo *fifo)
> &axis_fifo_debugfs_regs_fops);
> }
>
> -static int axis_fifo_parse_dt(struct axis_fifo *fifo)
> +
> +static int axis_fifo_get_u32(struct axis_fifo *fifo, const char *prop, u32 *val)
> {
> - int ret;
> - unsigned int value;
> - struct device_node *node = fifo->dt_device->of_node;
> + int ret = of_property_read_u32(fifo->dt_device->of_node, prop, val);
>
> - ret = of_property_read_u32(node, "xlnx,axi-str-rxd-tdata-width",
> - &value);
> if (ret) {
> - dev_err(fifo->dt_device, "missing xlnx,axi-str-rxd-tdata-width property\n");
> - goto end;
> - } else if (value != 32) {
> - dev_err(fifo->dt_device, "xlnx,axi-str-rxd-tdata-width only supports 32 bits\n");
> - ret = -EIO;
> - goto end;
> + dev_err(fifo->dt_device, "missing %s property\n", prop);
> + return ret;
> }
> + return 0;
> +}
>
> - ret = of_property_read_u32(node, "xlnx,axi-str-txd-tdata-width",
> - &value);
> - if (ret) {
> - dev_err(fifo->dt_device, "missing xlnx,axi-str-txd-tdata-width property\n");
> - goto end;
> - } else if (value != 32) {
> - dev_err(fifo->dt_device, "xlnx,axi-str-txd-tdata-width only supports 32 bits\n");
> - ret = -EIO;
> - goto end;
> - }
> +static int axis_fifo_parse_dt(struct axis_fifo *fifo)
> +{
> + u32 width;
>
> - ret = of_property_read_u32(node, "xlnx,rx-fifo-depth",
> - &fifo->rx_fifo_depth);
> - if (ret) {
> - dev_err(fifo->dt_device, "missing xlnx,rx-fifo-depth property\n");
> - ret = -EIO;
> - goto end;
> + if (axis_fifo_get_u32(fifo, "xlnx,axi-str-rxd-tdata-width", &width) || width != 32) {
> + dev_err(fifo->dt_device, "tdata-width only supports 32 bits\n");
Better to put "rx" in the error message
> + return -EIO;
> }
> -
> - ret = of_property_read_u32(node, "xlnx,tx-fifo-depth",
> - &fifo->tx_fifo_depth);
> - if (ret) {
> - dev_err(fifo->dt_device, "missing xlnx,tx-fifo-depth property\n");
> - ret = -EIO;
> - goto end;
> + if (axis_fifo_get_u32(fifo, "xlnx,axi-str-txd-tdata-width", &width) || width != 32) {
> + dev_err(fifo->dt_device, "tdata-width only supports 32 bits\n");
and "tx" here.
regards,
dan carpenter
> + return -EIO;
> }
prev parent reply other threads:[~2026-02-02 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 18:27 [PATCH v3 0/2] staging: axis-fifo: refactor and cleanup Gustavo Piaz da Silva
2026-01-31 18:27 ` [PATCH v3 1/2] staging: axis-fifo: align fifo depth types with OF API Gustavo Piaz da Silva
2026-01-31 18:27 ` [PATCH v3 2/2] staging: axis-fifo: refactor device tree parsing Gustavo Piaz da Silva
2026-02-02 8:32 ` Dan Carpenter [this message]
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=aYBhCBMkxb-TlVFH@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gshahrouzi@gmail.com \
--cc=gustavopiazdasilva2102@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox