From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: James Schulman <james.schulman@cirrus.com>
Cc: mark.rutland@arm.com, brian.austin@cirrus.com,
alsa-devel@alsa-project.org, paul.handrigan@cirrus.com,
lgirdwood@gmail.com, robh+dt@kernel.org
Subject: Re: [PATCH v2 2/2] ASoC: cs35l36: Add device tree documentation for CS35L36
Date: Wed, 12 Dec 2018 16:55:34 +0000 [thread overview]
Message-ID: <20181212165534.GR16508@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <1544130287-7303-2-git-send-email-james.schulman@cirrus.com>
On Thu, Dec 06, 2018 at 03:04:47PM -0600, James Schulman wrote:
> Add device tree documentation for Cirrus Logic CS35L36
> speaker amplifier
>
> Signed-off-by: James Schulman <james.schulman@cirrus.com>
> ---
> +Optional properties for the "cirrus,irq-config" Sub-node
> +
> + - cirrus,irq-drive-select : Selects the driver type of the selected interrupt
> + output.
> +
> + 0 = Open-drain
> + 1 = Push-pull (Default)
> +
> + - cirrus,irq-polarity : Selects the polarity of the selected interrupt output
> + when in push-pull mode. Note - when the selected interrupt output is in
> + open-drain mode, INT_POL_SEL must be set to 0.
> +
> + 0 = Active-low (Default)
> + 1 = Active-high
> +
Does this device tree entry in your example:
interrupts = <3 IRQ_TYPE_LEVEL_LOW>;
Not already convey what polarity you require? Adding a separate
entry seems unnecessary.
> + - cirrus,irq-gpio-select : Selects the pin to serve as the programmable
> + interrupt output.
> +
> + 0 = PDM_DATA / SWIRE_SD / INT (Default)
> + 1 = GPIO
> +
> + - cirrus,irq-output-enable : Enables or disables the selected interrupt output
> +
> + 0 = Disabled (Default)
> + 1 = Enabled
> +
Likewise here doesn't the presence/absence of the interrupts
entry convey whether you want the IRQ enabled?
> + - cirrus,irq-src-select : Selects the source of the selected interrupt output.
> +
> + 0 = PAC-based interrupt output
> + 1 = Interrupt handler (Default)
> +
Is there a use-case for this at the moment? This feels like it
might be worth dropping until it is necessary.
Thanks,
Charles
next prev parent reply other threads:[~2018-12-12 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 21:04 [PATCH v2 1/2] ASoC: cs35l36: Add support for Cirrus CS35L36 Amplifier James Schulman
2018-12-06 21:04 ` [PATCH v2 2/2] ASoC: cs35l36: Add device tree documentation for CS35L36 James Schulman
2018-12-12 16:55 ` Charles Keepax [this message]
2018-12-12 17:07 ` [PATCH v2 1/2] ASoC: cs35l36: Add support for Cirrus CS35L36 Amplifier Charles Keepax
2018-12-13 22:47 ` Schulman, James
-- strict thread matches above, loose matches on Subject: below --
2019-02-06 19:06 [PATCH v2 2/2] ASoC: cs35l36: Add device tree documentation for CS35L36 James Schulman
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=20181212165534.GR16508@imbe.wolfsonmicro.main \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=mark.rutland@arm.com \
--cc=paul.handrigan@cirrus.com \
--cc=robh+dt@kernel.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.