All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Turquette <mturquette@linaro.org>
To: Joachim  Eastwood <manabian@gmail.com>,
Cc: devicetree@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
	linux-clk@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/5] clk: add lpc18xx ccu clk driver
Date: Thu, 18 Jun 2015 15:45:38 -0700	[thread overview]
Message-ID: <20150618224538.9112.61682@quantum> (raw)
In-Reply-To: <CAGhQ9VwONWTULGUbGuf_2HbLpfU4pp8S49xdtoCcKcm1p=n7hg@mail.gmail.com>

Quoting Joachim Eastwood (2015-06-10 07:02:59)
> Hi Mike,
> 
> 
> > Hi Joachim,
> >
> > If it were me, I would have broken this up into two tables, one for each
> > CCU. In general I would structure the code to reflect the fact that two
> > different IP blocks are being accessed. This isn't a deal breaker but I
> > thought I would mention it in case you want to make the change.
> >
> > Otherwise this series looks good to me. Let me know if you plan a V5
> > submission.
> 
> If there is still time for 4.2 and you don't have any more comments on
> how the driver uses the DT bindings I would rather send a follow up
> patch that splits the ccu table for 4.3.
> 
> 
> > I can take patches #1-4 into the clk tree. Please add my Acked-by to
> > patch #5. I will create an immutable branch to share with the arm-soc
> > tree so that they can take #5 and have access to the dt-bindings
> > headers.
> 
> Sounds good. I'll talk to arm-soc team about it. But it isn't critical
> for me to get the DTS changes in for 4.2, but I would be very grateful
> for getting the drivers and headers in for 4.2 so that 4.3 is ready
> and doesn't have any header dependencies for all the driver DTS stuff.

Patches #1-4 applied to clk-next for 4.2.

Regards,
Mike

> 
> Thanks, Mike.
> 
> 
> regards,
> Joachim Eastwood

_______________________________________________
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: mturquette@linaro.org (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/5] clk: add lpc18xx ccu clk driver
Date: Thu, 18 Jun 2015 15:45:38 -0700	[thread overview]
Message-ID: <20150618224538.9112.61682@quantum> (raw)
In-Reply-To: <CAGhQ9VwONWTULGUbGuf_2HbLpfU4pp8S49xdtoCcKcm1p=n7hg@mail.gmail.com>

Quoting Joachim Eastwood (2015-06-10 07:02:59)
> Hi Mike,
> 
> 
> > Hi Joachim,
> >
> > If it were me, I would have broken this up into two tables, one for each
> > CCU. In general I would structure the code to reflect the fact that two
> > different IP blocks are being accessed. This isn't a deal breaker but I
> > thought I would mention it in case you want to make the change.
> >
> > Otherwise this series looks good to me. Let me know if you plan a V5
> > submission.
> 
> If there is still time for 4.2 and you don't have any more comments on
> how the driver uses the DT bindings I would rather send a follow up
> patch that splits the ccu table for 4.3.
> 
> 
> > I can take patches #1-4 into the clk tree. Please add my Acked-by to
> > patch #5. I will create an immutable branch to share with the arm-soc
> > tree so that they can take #5 and have access to the dt-bindings
> > headers.
> 
> Sounds good. I'll talk to arm-soc team about it. But it isn't critical
> for me to get the DTS changes in for 4.2, but I would be very grateful
> for getting the drivers and headers in for 4.2 so that 4.3 is ready
> and doesn't have any header dependencies for all the driver DTS stuff.

Patches #1-4 applied to clk-next for 4.2.

Regards,
Mike

> 
> Thanks, Mike.
> 
> 
> regards,
> Joachim Eastwood

WARNING: multiple messages have this Message-ID (diff)
From: Michael Turquette <mturquette@linaro.org>
To: Joachim Eastwood <manabian@gmail.com>
Cc: devicetree@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
	linux-clk@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/5] clk: add lpc18xx ccu clk driver
Date: Thu, 18 Jun 2015 15:45:38 -0700	[thread overview]
Message-ID: <20150618224538.9112.61682@quantum> (raw)
In-Reply-To: <CAGhQ9VwONWTULGUbGuf_2HbLpfU4pp8S49xdtoCcKcm1p=n7hg@mail.gmail.com>

Quoting Joachim Eastwood (2015-06-10 07:02:59)
> Hi Mike,
> 
> 
> > Hi Joachim,
> >
> > If it were me, I would have broken this up into two tables, one for each
> > CCU. In general I would structure the code to reflect the fact that two
> > different IP blocks are being accessed. This isn't a deal breaker but I
> > thought I would mention it in case you want to make the change.
> >
> > Otherwise this series looks good to me. Let me know if you plan a V5
> > submission.
> 
> If there is still time for 4.2 and you don't have any more comments on
> how the driver uses the DT bindings I would rather send a follow up
> patch that splits the ccu table for 4.3.
> 
> 
> > I can take patches #1-4 into the clk tree. Please add my Acked-by to
> > patch #5. I will create an immutable branch to share with the arm-soc
> > tree so that they can take #5 and have access to the dt-bindings
> > headers.
> 
> Sounds good. I'll talk to arm-soc team about it. But it isn't critical
> for me to get the DTS changes in for 4.2, but I would be very grateful
> for getting the drivers and headers in for 4.2 so that 4.3 is ready
> and doesn't have any header dependencies for all the driver DTS stuff.

Patches #1-4 applied to clk-next for 4.2.

Regards,
Mike

> 
> Thanks, Mike.
> 
> 
> regards,
> Joachim Eastwood

  reply	other threads:[~2015-06-18 22:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 20:31 [PATCH v4 0/5] Clk drivers for NXP LPC18xx family Joachim Eastwood
2015-05-28 20:31 ` Joachim Eastwood
2015-05-28 20:31 ` Joachim Eastwood
2015-05-28 20:31 ` [PATCH v4 1/5] clk: add lpc18xx cgu clk driver Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31 ` [PATCH v4 2/5] doc: dt: add documentation for lpc1850-cgu " Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31 ` [PATCH v4 3/5] clk: add lpc18xx ccu " Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-06-10  2:13   ` Michael Turquette
2015-06-10  2:13     ` Michael Turquette
2015-06-10  2:13     ` Michael Turquette
2015-06-10 14:02     ` Joachim Eastwood
2015-06-10 14:02       ` Joachim Eastwood
2015-06-10 14:02       ` Joachim Eastwood
2015-06-18 22:45       ` Michael Turquette [this message]
2015-06-18 22:45         ` Michael Turquette
2015-06-18 22:45         ` Michael Turquette
2015-06-19  5:17         ` Joachim Eastwood
2015-06-19  5:17           ` Joachim Eastwood
2015-06-19  5:17           ` Joachim Eastwood
2015-05-28 20:31 ` [PATCH v4 4/5] doc: dt: add documentation for lpc1850-ccu " Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31 ` [PATCH v4 5/5] ARM: dts: lpc18xx: add clock nodes for cgu and ccu Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood
2015-05-28 20:31   ` Joachim Eastwood

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=20150618224538.9112.61682@quantum \
    --to=mturquette@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=sboyd@codeaurora.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.