All of lore.kernel.org
 help / color / mirror / Atom feed
From: b51503@freescale.com (Bai Ping)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx: Fix the assigned-clock mismatch issue on imx6q/dl
Date: Tue, 15 Dec 2015 20:25:40 +0800	[thread overview]
Message-ID: <567006C4.8050906@freescale.com> (raw)
In-Reply-To: <CAOMZO5BKFqMKpRiM6hV43Ko7YcGHPEChSi1GEBMzg3oGo6_Lnw@mail.gmail.com>



On 2015/12/15 19:16, Fabio Estevam wrote:
> On Tue, Dec 15, 2015 at 6:52 AM, Shawn Guo <shawnguo@kernel.org> wrote:
>> On Mon, Dec 14, 2015 at 11:07:50AM +0800, Shawn Guo wrote:
>>> On Wed, Dec 09, 2015 at 04:15:55PM +0800, Bai Ping wrote:
>>>> The 'assigned-clock-parents' and 'assigned-clock-rates' list
>>>> should corresponding to the 'assigned-clocks' property clock list.
>>>>
>>>> Signed-off-by: Bai Ping <b51503@freescale.com>
>>> Applied, thanks.
>> As this essentially a fix to ed339363de1b ("ARM: dts: imx6qdl-sabreauto:
>> Allow HDMI and LVDS to work simultaneously"), I'm going to send it as a
>> fix with copying stable.
> Actually the mismatch exists since 97dae8590fa314c ("ARM: dts:
> imx6qdl-sabreauto: Add audio support").
>
>> @Fabio,
>>
>> Do you agree with the fix?
> It seems that even after this patch we still have a mismatch:
> assigned-clocks has 5 members and assigned-clock-parents has 4.
I think if it is the last clock in the assigned-clock list, the 
corresponding
'assigned-clock-parents' and 'assigned-clock-rates'  entry can be omitted.

BR
Jacky Bai

WARNING: multiple messages have this Message-ID (diff)
From: Bai Ping <b51503@freescale.com>
To: Fabio Estevam <festevam@gmail.com>, Shawn Guo <shawnguo@kernel.org>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: imx: Fix the assigned-clock mismatch issue on imx6q/dl
Date: Tue, 15 Dec 2015 20:25:40 +0800	[thread overview]
Message-ID: <567006C4.8050906@freescale.com> (raw)
In-Reply-To: <CAOMZO5BKFqMKpRiM6hV43Ko7YcGHPEChSi1GEBMzg3oGo6_Lnw@mail.gmail.com>



On 2015/12/15 19:16, Fabio Estevam wrote:
> On Tue, Dec 15, 2015 at 6:52 AM, Shawn Guo <shawnguo@kernel.org> wrote:
>> On Mon, Dec 14, 2015 at 11:07:50AM +0800, Shawn Guo wrote:
>>> On Wed, Dec 09, 2015 at 04:15:55PM +0800, Bai Ping wrote:
>>>> The 'assigned-clock-parents' and 'assigned-clock-rates' list
>>>> should corresponding to the 'assigned-clocks' property clock list.
>>>>
>>>> Signed-off-by: Bai Ping <b51503@freescale.com>
>>> Applied, thanks.
>> As this essentially a fix to ed339363de1b ("ARM: dts: imx6qdl-sabreauto:
>> Allow HDMI and LVDS to work simultaneously"), I'm going to send it as a
>> fix with copying stable.
> Actually the mismatch exists since 97dae8590fa314c ("ARM: dts:
> imx6qdl-sabreauto: Add audio support").
>
>> @Fabio,
>>
>> Do you agree with the fix?
> It seems that even after this patch we still have a mismatch:
> assigned-clocks has 5 members and assigned-clock-parents has 4.
I think if it is the last clock in the assigned-clock list, the 
corresponding
'assigned-clock-parents' and 'assigned-clock-rates'  entry can be omitted.

BR
Jacky Bai

  reply	other threads:[~2015-12-15 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  8:15 [PATCH] ARM: dts: imx: Fix the assigned-clock mismatch issue on imx6q/dl Bai Ping
2015-12-09  8:15 ` Bai Ping
2015-12-09  8:15 ` Bai Ping
2015-12-14  3:07 ` Shawn Guo
2015-12-14  3:07   ` Shawn Guo
2015-12-15  8:52   ` Shawn Guo
2015-12-15  8:52     ` Shawn Guo
2015-12-15 11:16     ` Fabio Estevam
2015-12-15 11:16       ` Fabio Estevam
2015-12-15 11:16       ` Fabio Estevam
2015-12-15 12:25       ` Bai Ping [this message]
2015-12-15 12:25         ` Bai Ping
2015-12-15 12:44         ` Fabio Estevam
2015-12-15 12:44           ` Fabio Estevam
2015-12-15 12:44           ` Fabio Estevam

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=567006C4.8050906@freescale.com \
    --to=b51503@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.