From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Kamel Bouhara <kamel.bouhara@bootlin.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v6 0/5] Microchip TCB Capture driver
Date: Wed, 15 Jul 2020 23:30:03 +0200 [thread overview]
Message-ID: <20200715213003.GD23553@piout.net> (raw)
In-Reply-To: <20200712143534.278ea3c7@archlinux>
Hi Jonathan,
On 12/07/2020 14:35:34+0100, Jonathan Cameron wrote:
> On Mon, 6 Jul 2020 13:43:42 +0200
> Kamel Bouhara <kamel.bouhara@bootlin.com> wrote:
>
> > Hello,
> >
> > Here is a new counter driver to support Microchip TCB capture devices.
> >
> > Each SoC has two TCB blocks, each one including three independent
> > channels.The following series adds support for two counter modes:
> > increase and quadrature decoder.
> >
> > As for the atmel clocksource and pwm, the counter driver needs to fill
> > some tcb capabilities in order to operate with the right configuration.
> > This is achieved in first patch of this series.
> >
> > Please feel free to comment.
>
> As far as I can see we have all the necessary acks etc and it looks
> good to me as well.
>
> Shall I do an immutable branch with the whole lot or should we split it
> up? Patches 1 and 5 need to go through the same tree, but bindings
> could go via another route. I'm also fine if the whole lot goes
> via the appropriate soc tree if that is easier.
>
I think the best would be an immutable branch as I have another series
that depends on the three preliminary patches that should go through the
clocksource/tip tree this cycle:
https://lore.kernel.org/linux-arm-kernel/20200710230813.1005150-1-alexandre.belloni@bootlin.com/
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-15 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:43 [PATCH v6 0/5] Microchip TCB Capture driver Kamel Bouhara
2020-07-06 11:43 ` [PATCH v6 1/5] ARM: at91: add atmel tcb capabilities Kamel Bouhara
2020-07-06 11:43 ` [PATCH v6 2/5] dt-bindings: atmel-tcb: convert bindings to json-schema Kamel Bouhara
2020-07-06 11:43 ` [PATCH v6 3/5] dt-bindings: microchip: atmel,at91rm9200-tcb: add sama5d2 compatible Kamel Bouhara
2020-07-09 21:05 ` [PATCH v6 3/5] dt-bindings: microchip: atmel, at91rm9200-tcb: " Rob Herring
2020-07-06 11:43 ` [PATCH v6 4/5] dt-bindings: counter: microchip-tcb-capture counter Kamel Bouhara
2020-07-06 11:43 ` [PATCH v6 5/5] counter: Add microchip TCB capture counter Kamel Bouhara
2020-07-06 19:22 ` William Breathitt Gray
2020-07-07 6:48 ` Kamel Bouhara
2020-07-12 13:35 ` [PATCH v6 0/5] Microchip TCB Capture driver Jonathan Cameron
2020-07-15 21:30 ` Alexandre Belloni [this message]
2020-07-20 13:38 ` Jonathan Cameron
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=20200715213003.GD23553@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vilhelm.gray@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).