devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Scally <dan.scally@ideasonboard.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-renesas-soc@vger.kernel.org, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Magnus Damm <magnus.damm@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 jacopo.mondi@ideasonboard.com, biju.das.jz@bp.renesas.com,
	 laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v4 2/3] media: platform: Add Renesas Input Video Control block driver
Date: Wed, 30 Jul 2025 16:10:38 +0200	[thread overview]
Message-ID: <CAMuHMdXhUiPiQsK_gWhb_B9mEhwM-KBg7WMzq3bPBpbzxxWRrw@mail.gmail.com> (raw)
In-Reply-To: <20250714-ivc-v4-2-534ea488c738@ideasonboard.com>

Hi Daniel,

On Mon, 14 Jul 2025 at 17:19, Daniel Scally <dan.scally@ideasonboard.com> wrote:
> Add a driver for the Input Video Control block in an RZ/V2H SoC which
> feeds data into the Arm Mali-C55 ISP.
>
> Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>

Thanks for your patch!

> --- /dev/null
> +++ b/drivers/media/platform/renesas/rzv2h-ivc/rzv2h-ivc-dev.c

> +static int rzv2h_ivc_get_hardware_resources(struct rzv2h_ivc *ivc,
> +                                           struct platform_device *pdev)
> +{
> +       const char * const resource_names[RZV2H_IVC_NUM_HW_RESOURCES] = {

static

> +               "reg",
> +               "axi",
> +               "isp",
> +       };

> +static int rzv2h_ivc_probe(struct platform_device *pdev)
> +{
> +       struct device *dev = &pdev->dev;
> +       struct rzv2h_ivc *ivc;
> +       int ret;
> +
> +       ivc = devm_kzalloc(dev, sizeof(*ivc), GFP_KERNEL);
> +       if (!ivc)
> +               return -ENOMEM;
> +
> +       ivc->dev = dev;
> +       platform_set_drvdata(pdev, ivc);
> +       mutex_init(&ivc->lock);
> +       spin_lock_init(&ivc->spinlock);
> +
> +       ret = rzv2h_ivc_get_hardware_resources(ivc, pdev);
> +       if (ret)
> +               return ret;
> +
> +       pm_runtime_set_autosuspend_delay(dev, 2000);
> +       pm_runtime_use_autosuspend(dev);
> +       pm_runtime_enable(dev);
> +
> +       ivc->irqnum = platform_get_irq(pdev, 0);
> +       if (ivc->irqnum < 0) {
> +               dev_err(dev, "failed to get interrupt\n");

No need to print anything, as platform_get_irq() already calls
dev_err_probe() on failure.

> +               return ret;
> +       }
> +
> +       ret = rzv2h_ivc_initialise_subdevice(ivc);
> +       if (ret)
> +               return ret;
> +
> +       return 0;
> +}

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2025-07-30 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 15:19 [PATCH v4 0/3] Add Input Video Control Block driver for RZ/V2H Daniel Scally
2025-07-14 15:19 ` [PATCH v4 1/3] dt-bindings: media: Add bindings for the RZ/V2H IVC block Daniel Scally
2025-07-24 15:55   ` Lad, Prabhakar
2025-07-14 15:19 ` [PATCH v4 2/3] media: platform: Add Renesas Input Video Control block driver Daniel Scally
2025-07-22  9:40   ` Jacopo Mondi
2025-07-23 21:17     ` Dan Scally
2025-07-24 16:52   ` Lad, Prabhakar
2025-07-24 18:04     ` Dan Scally
2025-07-24 20:18       ` Lad, Prabhakar
2025-07-30 14:10   ` Geert Uytterhoeven [this message]
2025-07-14 15:19 ` [PATCH v4 3/3] MAINTAINERS: Add entry for rzv2h-ivc driver Daniel Scally
2025-07-14 16:07   ` 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=CAMuHMdXhUiPiQsK_gWhb_B9mEhwM-KBg7WMzq3bPBpbzxxWRrw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@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).