All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@v>
Subject: RE: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
Date: Tue, 19 Mar 2019 11:22:35 +0000	[thread overview]
Message-ID: <TY1PR01MB1770A2ACD8287D3675270A0AC0400@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY1PR01MB177071330C7BD433A701F728C0960@TY1PR01MB1770.jpnprd01.prod.outlook.com>

Hello Simon,

> From: devicetree-owner@vger.kernel.org <devicetree-owner@vger.kernel.org> On Behalf Of Fabrizio Castro
> Sent: 28 January 2019 14:49
> Subject: RE: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> 
> > From: Simon Horman <horms@verge.net.au>
> > Sent: 28 January 2019 13:01
> > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> >
> > On Fri, Jan 25, 2019 at 11:33:41AM +0000, Fabrizio Castro wrote:
> > > Hello Simon,
> > >
> > > Thank you for your feedback!
> > >
> > > > From: Simon Horman <horms@verge.net.au>
> > > > Sent: 24 January 2019 10:01
> > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > >
> > > > On Wed, Jan 23, 2019 at 12:18:45PM +0000, Fabrizio Castro wrote:
> > > > > Hello Geert,
> > > > >
> > > > > Thank you for your feedback!
> > > > >
> > > > > > From: Geert Uytterhoeven <geert@linux-m68k.org>
> > > > > > Sent: 23 January 2019 12:08
> > > > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > > > >
> > > > > > Hi Fabrizio,
> > > > > >
> > > > > > On Wed, Jan 23, 2019 at 1:01 PM Fabrizio Castro
> > > > > > <fabrizio.castro@bp.renesas.com> wrote:
> > > > > > > > From: Simon Horman <horms@verge.net.au>
> > > > > > > > Sent: 23 January 2019 11:38
> > > > > > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > > > > > >
> > > > > > > > On Wed, Jan 23, 2019 at 10:51:23AM +0100, Simon Horman wrote:
> > > > > > > > > On Fri, Jan 18, 2019 at 01:13:53PM +0100, Simon Horman wrote:
> > > > > > > > > > On Thu, Jan 17, 2019 at 02:54:15PM +0000, Fabrizio Castro wrote:
> > > > > > > > > > > According to the latest information, clkp2 is available on RZ/G2.
> > > > > > > > > > > Modify CAN0 and CAN1 nodes accordingly.
> > > > > > > > > > >
> > > > > > > > > > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > > > > > > > > > > Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> > > > > >
> > > > > > > > > Thanks again, applied for v5.1.
> > > > > > > >
> > > > > > > > Sorry, I was a little hasty there.
> > > > > > > >
> > > > > > > > This patch depends on the presence of R8A774A1_CLK_CANFD which
> > > > > > > > (rightly) is added in a different patch in this series which is to
> > > > > > > > go upstream via a different tree.
> > > > > > > >
> > > > > > > > I have dropped this patch for now. I think there are two solution to this
> > > > > > > > problem.
> > > > > > > >
> > > > > > > > 1. Provide a version of this patch which uses a numeric index instead of
> > > > > > > >    R8A774A1_CLK_CANFD. And then, once R8A774A1_CLK_CANFD is present in an
> > > > > > > >    RC release provide a patch to switch to using R8A774A1_CLK_CANFD.
> > > > > > > >
> > > > > > > > 2. Defer this patch until R8A774A1_CLK_CANFD is present in an RC release.
> > > > > > >
> > > > > > > Yeah, my personal preference is solution 2.
> > > > > >
> > > > > > Note that solution 2 will probably defer the DT patch to v5.2.
> > > > >
> > > > > Yeah, my understanding is that even if we chose solution 1 we would still
> > > > > need to be waiting for v5.2 for the patch to switch to using
> > > > > R8A774A1_CLK_CANFD to appear in a rc, therefore I think solution 2 is
> > > > > fine.
> > > >
> > > > Your understanding is the same as mine.
> > > >
> > > > I do seem some slight value in option 1 in terms of getting the change,
> > > > less the minor issue of using an index rather than a symbol, upstream
> > > > earlier. But I do not feel strongly about this.
> > > >
> > > > I am marking this patch as deferred. Please repost or otherwise ping me
> > > > when you would like to revisit this topic.
> > >
> > > Thank you. Will do.
> >
> > Thanks.
> >
> > I believe "[10/11] arm64: dts: renesas: r8a774c0: Add clkp2 clock to CAN nodes"
> > falls into the same category. I have marked it as deferred accordingly.
> 
> Ok, thank you Simon

My understanding is that this patch can now be taken, and it still applies neatly.

Thanks,
Fab

> 
> Fab
> 
> 
> 
> 
> Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England &
> Wales under Registered No. 04586709.

WARNING: multiple messages have this Message-ID (diff)
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: RE: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
Date: Tue, 19 Mar 2019 11:22:35 +0000	[thread overview]
Message-ID: <TY1PR01MB1770A2ACD8287D3675270A0AC0400@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY1PR01MB177071330C7BD433A701F728C0960@TY1PR01MB1770.jpnprd01.prod.outlook.com>

Hello Simon,

> From: devicetree-owner@vger.kernel.org <devicetree-owner@vger.kernel.org> On Behalf Of Fabrizio Castro
> Sent: 28 January 2019 14:49
> Subject: RE: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> 
> > From: Simon Horman <horms@verge.net.au>
> > Sent: 28 January 2019 13:01
> > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> >
> > On Fri, Jan 25, 2019 at 11:33:41AM +0000, Fabrizio Castro wrote:
> > > Hello Simon,
> > >
> > > Thank you for your feedback!
> > >
> > > > From: Simon Horman <horms@verge.net.au>
> > > > Sent: 24 January 2019 10:01
> > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > >
> > > > On Wed, Jan 23, 2019 at 12:18:45PM +0000, Fabrizio Castro wrote:
> > > > > Hello Geert,
> > > > >
> > > > > Thank you for your feedback!
> > > > >
> > > > > > From: Geert Uytterhoeven <geert@linux-m68k.org>
> > > > > > Sent: 23 January 2019 12:08
> > > > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > > > >
> > > > > > Hi Fabrizio,
> > > > > >
> > > > > > On Wed, Jan 23, 2019 at 1:01 PM Fabrizio Castro
> > > > > > <fabrizio.castro@bp.renesas.com> wrote:
> > > > > > > > From: Simon Horman <horms@verge.net.au>
> > > > > > > > Sent: 23 January 2019 11:38
> > > > > > > > Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes
> > > > > > > >
> > > > > > > > On Wed, Jan 23, 2019 at 10:51:23AM +0100, Simon Horman wrote:
> > > > > > > > > On Fri, Jan 18, 2019 at 01:13:53PM +0100, Simon Horman wrote:
> > > > > > > > > > On Thu, Jan 17, 2019 at 02:54:15PM +0000, Fabrizio Castro wrote:
> > > > > > > > > > > According to the latest information, clkp2 is available on RZ/G2.
> > > > > > > > > > > Modify CAN0 and CAN1 nodes accordingly.
> > > > > > > > > > >
> > > > > > > > > > > Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > > > > > > > > > > Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> > > > > >
> > > > > > > > > Thanks again, applied for v5.1.
> > > > > > > >
> > > > > > > > Sorry, I was a little hasty there.
> > > > > > > >
> > > > > > > > This patch depends on the presence of R8A774A1_CLK_CANFD which
> > > > > > > > (rightly) is added in a different patch in this series which is to
> > > > > > > > go upstream via a different tree.
> > > > > > > >
> > > > > > > > I have dropped this patch for now. I think there are two solution to this
> > > > > > > > problem.
> > > > > > > >
> > > > > > > > 1. Provide a version of this patch which uses a numeric index instead of
> > > > > > > >    R8A774A1_CLK_CANFD. And then, once R8A774A1_CLK_CANFD is present in an
> > > > > > > >    RC release provide a patch to switch to using R8A774A1_CLK_CANFD.
> > > > > > > >
> > > > > > > > 2. Defer this patch until R8A774A1_CLK_CANFD is present in an RC release.
> > > > > > >
> > > > > > > Yeah, my personal preference is solution 2.
> > > > > >
> > > > > > Note that solution 2 will probably defer the DT patch to v5.2.
> > > > >
> > > > > Yeah, my understanding is that even if we chose solution 1 we would still
> > > > > need to be waiting for v5.2 for the patch to switch to using
> > > > > R8A774A1_CLK_CANFD to appear in a rc, therefore I think solution 2 is
> > > > > fine.
> > > >
> > > > Your understanding is the same as mine.
> > > >
> > > > I do seem some slight value in option 1 in terms of getting the change,
> > > > less the minor issue of using an index rather than a symbol, upstream
> > > > earlier. But I do not feel strongly about this.
> > > >
> > > > I am marking this patch as deferred. Please repost or otherwise ping me
> > > > when you would like to revisit this topic.
> > >
> > > Thank you. Will do.
> >
> > Thanks.
> >
> > I believe "[10/11] arm64: dts: renesas: r8a774c0: Add clkp2 clock to CAN nodes"
> > falls into the same category. I have marked it as deferred accordingly.
> 
> Ok, thank you Simon

My understanding is that this patch can now be taken, and it still applies neatly.

Thanks,
Fab

> 
> Fab
> 
> 
> 
> 
> Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England &
> Wales under Registered No. 04586709.

  reply	other threads:[~2019-03-19 11:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 14:54 [PATCH 0/3] Correct CAN clocks definition Fabrizio Castro
2019-01-17 14:54 ` [PATCH 1/3] clk: renesas: r8a774a1: Add missing CANFD clock Fabrizio Castro
2019-01-18 12:14   ` Simon Horman
2019-01-21 13:00   ` Geert Uytterhoeven
2019-01-21 13:00     ` Geert Uytterhoeven
2019-01-17 14:54 ` [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes Fabrizio Castro
2019-01-18 12:13   ` Simon Horman
2019-01-23  9:51     ` Simon Horman
2019-01-23 11:38       ` Simon Horman
2019-01-23 12:00         ` Fabrizio Castro
2019-01-23 12:00           ` Fabrizio Castro
2019-01-23 12:07           ` Geert Uytterhoeven
2019-01-23 12:07             ` Geert Uytterhoeven
2019-01-23 12:18             ` Fabrizio Castro
2019-01-23 12:18               ` Fabrizio Castro
2019-01-24 10:01               ` Simon Horman
2019-01-24 10:01                 ` Simon Horman
2019-01-25 11:33                 ` Fabrizio Castro
2019-01-25 11:33                   ` Fabrizio Castro
2019-01-28 13:01                   ` Simon Horman
2019-01-28 13:01                     ` Simon Horman
2019-01-28 14:49                     ` Fabrizio Castro
2019-01-28 14:49                       ` Fabrizio Castro
2019-03-19 11:22                       ` Fabrizio Castro [this message]
2019-03-19 11:22                         ` Fabrizio Castro
2019-03-19 11:55                         ` Simon Horman
2019-03-19 11:55                           ` Simon Horman
2019-01-17 14:54 ` [PATCH 3/3] dt-bindings: can: rcar_canfd: Document r8a774a1 support Fabrizio Castro
2019-01-18 12:13   ` Simon Horman
2019-02-18 20:33   ` Rob Herring
2019-02-18 20:33     ` Rob Herring
2019-03-01 12:06   ` Fabrizio Castro
2019-03-01 12:06     ` Fabrizio Castro

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=TY1PR01MB1770A2ACD8287D3675270A0AC0400@TY1PR01MB1770.jpnprd01.prod.outlook.com \
    --to=fabrizio.castro@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-clk@v \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=mkl@pengutronix.de \
    --cc=mturquette@baylibre.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=wg@grandegger.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.