From: Stephen Boyd <sboyd@kernel.org>
To: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Emma Anholt <emma@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Ripard <maxime@cerno.tech>,
Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime@cerno.tech>,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-clk@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
Dom Cobley <popcornmix@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header
Date: Fri, 14 Oct 2022 12:31:39 -0700 [thread overview]
Message-ID: <20221014193141.A48C8C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220815-rpi-fix-4k-60-v3-2-fc56729d11fe@cerno.tech>
Quoting Maxime Ripard (2022-10-13 02:13:09)
> We'll need the clock IDs in more drivers than just the clock driver from
> now on, so let's move them in the firmware header.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Emma Anholt <emma@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Ripard <maxime@cerno.tech>,
Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime@cerno.tech>,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-clk@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
Dom Cobley <popcornmix@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header
Date: Fri, 14 Oct 2022 12:31:39 -0700 [thread overview]
Message-ID: <20221014193141.A48C8C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220815-rpi-fix-4k-60-v3-2-fc56729d11fe@cerno.tech>
Quoting Maxime Ripard (2022-10-13 02:13:09)
> We'll need the clock IDs in more drivers than just the clock driver from
> now on, so let's move them in the firmware header.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Emma Anholt <emma@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Ripard <maxime@cerno.tech>,
Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rpi-kernel@lists.infradead.org,
Dom Cobley <popcornmix@gmail.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH v3 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header
Date: Fri, 14 Oct 2022 12:31:39 -0700 [thread overview]
Message-ID: <20221014193141.A48C8C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220815-rpi-fix-4k-60-v3-2-fc56729d11fe@cerno.tech>
Quoting Maxime Ripard (2022-10-13 02:13:09)
> We'll need the clock IDs in more drivers than just the clock driver from
> now on, so let's move them in the firmware header.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2022-10-14 19:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:13 [PATCH v3 0/7] drm/vc4: Fix the core clock behaviour Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` [PATCH v3 1/7] firmware: raspberrypi: Introduce rpi_firmware_find_node() Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-14 19:43 ` Florian Fainelli
2022-10-14 19:43 ` Florian Fainelli
2022-10-14 19:43 ` Florian Fainelli
2022-10-18 7:32 ` Maxime Ripard
2022-10-18 7:32 ` Maxime Ripard
2022-10-18 7:32 ` Maxime Ripard
2022-10-13 9:13 ` [PATCH v3 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-14 19:31 ` Stephen Boyd [this message]
2022-10-14 19:31 ` Stephen Boyd
2022-10-14 19:31 ` Stephen Boyd
2022-10-14 19:44 ` Florian Fainelli
2022-10-14 19:44 ` Florian Fainelli
2022-10-14 19:44 ` Florian Fainelli
2022-10-13 9:13 ` [PATCH v3 3/7] firmware: raspberrypi: Provide a helper to query a clock max rate Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-14 19:45 ` Florian Fainelli
2022-10-14 19:45 ` Florian Fainelli
2022-10-14 19:45 ` Florian Fainelli
2022-10-13 9:13 ` [PATCH v3 4/7] drm/vc4: hdmi: Fix hdmi_enable_4kp60 detection Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` [PATCH v3 5/7] drm/vc4: hdmi: Rework hdmi_enable_4kp60 detection code Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` [PATCH v3 6/7] drm/vc4: hdmi: Add more checks for 4k resolutions Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` [PATCH v3 7/7] drm/vc4: Make sure we don't end up with a core clock too high Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
2022-10-13 9:13 ` Maxime Ripard
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=20221014193141.A48C8C433C1@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=f.fainelli@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.