public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: maxime@cerno.tech, Daniel Vetter <daniel@ffwll.ch>,
	Emma Anholt <emma@anholt.net>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Maxime Ripard <mripard@kernel.org>, Ray Jui <rjui@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	David Airlie <airlied@linux.ie>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, Dom Cobley <popcornmix@gmail.com>,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/7] firmware: raspberrypi: Introduce rpi_firmware_find_node()
Date: Mon, 24 Oct 2022 12:19:08 -0700	[thread overview]
Message-ID: <17868eda-d450-8780-18b7-e52af86b3d3e@gmail.com> (raw)
In-Reply-To: <20220815-rpi-fix-4k-60-v4-1-a1b40526df3e@cerno.tech>

On 10/20/22 02:12, maxime@cerno.tech wrote:
> A significant number of RaspberryPi drivers using the firmware don't
> have a phandle to it, so end up scanning the device tree to find a node
> with the firmware compatible.
> 
> That code is duplicated everywhere, so let's introduce a helper instead.
> 
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

Acked-by: Florian Fainelli <f.fainelli@gmail.com>

Thanks for re-ordering the rpi_firmware_of_match array and avoiding a 
forward declaration that I was initially confused about in v3.
-- 
Florian


  reply	other threads:[~2022-10-24 21:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  9:12 [PATCH v4 0/7] drm/vc4: Fix the core clock behaviour maxime
2022-10-20  9:12 ` [PATCH v4 1/7] firmware: raspberrypi: Introduce rpi_firmware_find_node() maxime
2022-10-24 19:19   ` Florian Fainelli [this message]
2022-10-20  9:12 ` [PATCH v4 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header maxime
2022-10-20  9:12 ` [PATCH v4 3/7] firmware: raspberrypi: Provide a helper to query a clock max rate maxime
2022-10-20  9:12 ` [PATCH v4 4/7] drm/vc4: hdmi: Fix hdmi_enable_4kp60 detection maxime
2022-10-26 15:27   ` Dave Stevenson
2022-10-26 15:36     ` Dave Stevenson
2022-10-26 16:10       ` maxime
2022-10-20  9:12 ` [PATCH v4 5/7] drm/vc4: hdmi: Rework hdmi_enable_4kp60 detection code maxime
2022-10-26 16:00   ` Dave Stevenson
2022-10-26 16:05     ` Dave Stevenson
2022-10-26 16:14     ` maxime
2022-10-20  9:12 ` [PATCH v4 6/7] drm/vc4: hdmi: Add more checks for 4k resolutions maxime
2022-10-26 16:06   ` Dave Stevenson
2022-10-20  9:12 ` [PATCH v4 7/7] drm/vc4: Make sure we don't end up with a core clock too high maxime
2022-10-26 16:09   ` Dave Stevenson

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=17868eda-d450-8780-18b7-e52af86b3d3e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=airlied@linux.ie \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=maxime@cerno.tech \
    --cc=mripard@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=popcornmix@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=sboyd@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.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