From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Kamel Bouhara <kamel.bouhara@bootlin.com>, jic23@kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-iio@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] ARM: at91: add atmel tcb capabilities
Date: Fri, 17 Apr 2020 09:56:35 -0400 [thread overview]
Message-ID: <20200417135635.GA94725@icarus> (raw)
In-Reply-To: <20200415130455.2222019-2-kamel.bouhara@bootlin.com>
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
On Wed, Apr 15, 2020 at 03:04:53PM +0200, Kamel Bouhara wrote:
> Some atmel socs have extra tcb capabilities that allow using a generic
> clock source or enabling a quadrature decoder.
>
> Signed-off-by: Kamel Bouhara <kamel.bouhara@bootlin.com>
Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> ---
> Changes from v3:
> - Added missing kernel doc for new elements introduced in structure
> atmel_tcb_config.
>
> Changes from v2:
> - Fixed first patch not applying on mainline
>
> include/soc/at91/atmel_tcb.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/soc/at91/atmel_tcb.h b/include/soc/at91/atmel_tcb.h
> index c3c7200ce151..1d7071dc0bca 100644
> --- a/include/soc/at91/atmel_tcb.h
> +++ b/include/soc/at91/atmel_tcb.h
> @@ -36,9 +36,14 @@ struct clk;
> /**
> * struct atmel_tcb_config - SoC data for a Timer/Counter Block
> * @counter_width: size in bits of a timer counter register
> + * @has_gclk: boolean indicating if a timer counter has a generic clock
> + * @has_qdec: boolean indicating if a timer counter has a quadrature
> + * decoder.
> */
> struct atmel_tcb_config {
> size_t counter_width;
> + bool has_gclk;
> + bool has_qdec;
> };
>
> /**
> --
> 2.25.0
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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
next prev parent reply other threads:[~2020-04-17 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:04 [PATCH v3 0/3] Microchip TCB Capture driver Kamel Bouhara
2020-04-15 13:04 ` [PATCH v3 1/3] ARM: at91: add atmel tcb capabilities Kamel Bouhara
2020-04-17 13:56 ` William Breathitt Gray [this message]
2020-04-18 18:23 ` Jonathan Cameron
2020-04-18 23:44 ` Alexandre Belloni
2020-04-15 13:04 ` [PATCH v3 2/3] dt-bindings: counter: microchip-tcb-capture counter Kamel Bouhara
2020-04-17 13:58 ` William Breathitt Gray
2020-04-18 18:24 ` Jonathan Cameron
2020-04-20 22:21 ` Rob Herring
2020-04-15 13:04 ` [PATCH v3 3/3] counter: Add microchip TCB capture counter Kamel Bouhara
2020-04-17 14:06 ` William Breathitt Gray
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=20200417135635.GA94725@icarus \
--to=vilhelm.gray@gmail.com \
--cc=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=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).