All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Guillaume Gardet <Guillaume.Gardet@arm.com>,
	"Ivan T. Ivanov" <iivanov@suse.de>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	"bcm-kernel-feedback-list@broadcom.com" 
	<bcm-kernel-feedback-list@broadcom.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-rpi-kernel@lists.infradead.org" 
	<linux-rpi-kernel@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>, nd <nd@arm.com>
Subject: Re: [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks
Date: Thu, 12 May 2022 09:57:37 +0200	[thread overview]
Message-ID: <20220512075737.mpipy7rmixwfwpyl@houat> (raw)
In-Reply-To: <6066bd9d-b53b-0a91-7440-98244c2d55c2@i2se.com>

[-- Attachment #1: Type: text/plain, Size: 779 bytes --]

On Wed, May 11, 2022 at 08:10:50AM +0200, Stefan Wahren wrote:
> Am 10.05.22 um 15:30 schrieb Maxime Ripard:
> > Hi,
> > 
> > On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote:
> > > May I ask what's the status/plan of  this patch series?
> > As far as I know it hasn't been merged yet.
> > 
> > > It seems it has not been merged yet, and I know we are a bit late in
> > > the 5.18 schedule, but I think this is a good fix for 5.18.
> > Fix for what? I don't think this series fix any bug?
>
> This seems to be a "fix" for the Frankenstone scenario: mainline kernel +
> vendor DT

Did we ever support this?

I don't think we did, so even though it can be nice to improve that
situation, I don't think it's worth sending this to stable

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Guillaume Gardet <Guillaume.Gardet@arm.com>,
	"Ivan T. Ivanov" <iivanov@suse.de>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	"bcm-kernel-feedback-list@broadcom.com"
	<bcm-kernel-feedback-list@broadcom.com>,
	 "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-rpi-kernel@lists.infradead.org"
	<linux-rpi-kernel@lists.infradead.org>,
	 "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,  nd <nd@arm.com>
Subject: Re: [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks
Date: Thu, 12 May 2022 09:57:37 +0200	[thread overview]
Message-ID: <20220512075737.mpipy7rmixwfwpyl@houat> (raw)
In-Reply-To: <6066bd9d-b53b-0a91-7440-98244c2d55c2@i2se.com>


[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]

On Wed, May 11, 2022 at 08:10:50AM +0200, Stefan Wahren wrote:
> Am 10.05.22 um 15:30 schrieb Maxime Ripard:
> > Hi,
> > 
> > On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote:
> > > May I ask what's the status/plan of  this patch series?
> > As far as I know it hasn't been merged yet.
> > 
> > > It seems it has not been merged yet, and I know we are a bit late in
> > > the 5.18 schedule, but I think this is a good fix for 5.18.
> > Fix for what? I don't think this series fix any bug?
>
> This seems to be a "fix" for the Frankenstone scenario: mainline kernel +
> vendor DT

Did we ever support this?

I don't think we did, so even though it can be nice to improve that
situation, I don't think it's worth sending this to stable

Maxime

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-12  7:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:57 [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Ivan T. Ivanov
2022-04-28  6:57 ` Ivan T. Ivanov
2022-04-28  6:57 ` [PATCH v4 1/3] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov
2022-04-28  6:57   ` Ivan T. Ivanov
2022-04-28  6:57 ` [PATCH v4 2/3] clk: bcm: rpi: Handle pixel clock in firmware Ivan T. Ivanov
2022-04-28  6:57   ` Ivan T. Ivanov
2022-04-28  6:57 ` [PATCH v4 3/3] clk: bcm: rpi: Add support for VEC clock Ivan T. Ivanov
2022-04-28  6:57   ` Ivan T. Ivanov
2022-04-28  8:03   ` Maxime Ripard
2022-04-28  8:03     ` Maxime Ripard
2022-05-10 13:20 ` [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Guillaume Gardet
2022-05-10 13:20   ` Guillaume Gardet
2022-05-10 13:30   ` Maxime Ripard
2022-05-10 13:30     ` Maxime Ripard
2022-05-11  6:10     ` Stefan Wahren
2022-05-11  6:10       ` Stefan Wahren
2022-05-12  7:57       ` Maxime Ripard [this message]
2022-05-12  7:57         ` Maxime Ripard
2022-05-12  8:10         ` Ivan Ivanov
2022-05-12  8:53           ` Maxime Ripard
2022-05-12  8:53             ` Maxime Ripard
2022-05-12  9:03             ` Ivan Ivanov
2022-07-10 11:12     ` Stefan Wahren
2022-07-10 11:12       ` Stefan Wahren
2022-07-11  7:02       ` Ivan T. Ivanov
2022-07-11  7:02         ` Ivan T. Ivanov
2022-07-11 11:55         ` Stefan Wahren
2022-07-11 11:55           ` Stefan Wahren
2022-08-23 22:54           ` Stephen Boyd
2022-05-26 11:36 ` Ivan T. Ivanov
2022-05-26 11:36   ` Ivan T. Ivanov
2022-06-21 15:30   ` Florian Fainelli
2022-06-21 15:30     ` Florian Fainelli

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=20220512075737.mpipy7rmixwfwpyl@houat \
    --to=maxime@cerno.tech \
    --cc=Guillaume.Gardet@arm.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=iivanov@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=nd@arm.com \
    --cc=nsaenz@kernel.org \
    --cc=sboyd@kernel.org \
    --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.