From: Michael Walle <michael@walle.cc>
To: william.gray@linaro.org
Cc: andriy.shevchenko@linux.intel.com, brgl@bgdev.pl,
broonie@kernel.org, jay.dolan@accesio.com, jhentges@accesio.com,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, quarium@gmail.com,
Michael Walle <michael@walle.cc>
Subject: Re: [PATCH v4 2/3] gpio: pcie-idio-24: Migrate to the regmap API
Date: Mon, 6 Mar 2023 15:33:09 +0100 [thread overview]
Message-ID: <20230306143309.758690-1-michael@walle.cc> (raw)
In-Reply-To: <b96429c66e7caca05d9fb93805e11650fdbad312.1678106722.git.william.gray@linaro.org>
> The regmap API supports IO port accessors so we can take advantage of
> regmap abstractions rather than handling access to the device registers
> directly in the driver.
>
> For the PCIe-IDIO-24 series of devices, the following BARs are
> available:
>
> BAR[0]: memory mapped PEX8311
> BAR[1]: I/O mapped PEX8311
> BAR[2]: I/O mapped card registers
>
> There are 24 FET Output lines, 24 Isolated Input lines, and 8 TTL/CMOS
> lines (which may be configured for either output or input). The GPIO
> lines are exposed by the following card registers:
>
> Base +0x0-0x2 (Read/Write): FET Outputs
> Base +0xB (Read/Write): TTL/CMOS
> Base +0x4-0x6 (Read): Isolated Inputs
> Base +0x7 (Read): TTL/CMOS
>
> In order for the device to support interrupts, the PLX PEX8311 internal
> PCI wire interrupt and local interrupt input must first be enabled.
>
> The following card registers for Change-Of-State may be used:
>
> Base +0x8-0xA (Read): COS Status Inputs
> Base +0x8-0xA (Write): COS Clear Inputs
> Base +0xB (Read): COS Status TTL/CMOS
> Base +0xB (Write): COS Clear TTL/CMOS
> Base +0xE (Read/Write): COS Enable
>
> The COS Enable register is used to enable/disable interrupts and
> configure the interrupt levels; each bit maps to a group of eight inputs
> as described below:
>
> Bit 0: IRQ EN Rising Edge IN0-7
> Bit 1: IRQ EN Rising Edge IN8-15
> Bit 2: IRQ EN Rising Edge IN16-23
> Bit 3: IRQ EN Rising Edge TTL0-7
> Bit 4: IRQ EN Falling Edge IN0-7
> Bit 5: IRQ EN Falling Edge IN8-15
> Bit 6: IRQ EN Falling Edge IN16-23
> Bit 7: IRQ EN Falling Edge TTL0-7
>
> An interrupt is asserted when a change-of-state matching the interrupt
> level configuration respective for a particular group of eight inputs
> with enabled COS is detected.
>
> The COS Status registers may be read to determine which inputs have
> changed; if interrupts were enabled, an IRQ will be generated for the
> set bits in these registers. Writing the value read from the COS Status
> register back to the respective COS Clear register will clear just those
> interrupts.
>
> Cc: Arnaud de Turckheim <quarium@gmail.com>
> Cc: John Hentges <jhentges@accesio.com>
> Cc: Jay Dolan <jay.dolan@accesio.com>
> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
FWIW, the gpio-regmap part looks good:
Reviewed-by: Michael Walle <michael@walle.cc>
-michael
next prev parent reply other threads:[~2023-03-06 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 12:59 [PATCH v4 0/3] Migrate the PCIe-IDIO-24 and WS16C48 GPIO drivers to the regmap API William Breathitt Gray
2023-03-06 12:59 ` [PATCH v4 1/3] regmap: Pass irq_drv_data as a parameter for set_type_config() William Breathitt Gray
2023-03-06 12:59 ` [PATCH v4 2/3] gpio: pcie-idio-24: Migrate to the regmap API William Breathitt Gray
2023-03-06 14:24 ` Andy Shevchenko
2023-03-08 2:29 ` William Breathitt Gray
2023-03-06 14:33 ` Michael Walle [this message]
2023-03-06 12:59 ` [PATCH v4 3/3] gpio: ws16c48: " William Breathitt Gray
2023-03-06 14:20 ` Andy Shevchenko
2023-03-08 2:51 ` William Breathitt Gray
2023-03-08 13:06 ` Andy Shevchenko
2023-03-09 19:33 ` William Breathitt Gray
2023-03-06 14:35 ` Michael Walle
2023-03-06 14:25 ` [PATCH v4 0/3] Migrate the PCIe-IDIO-24 and WS16C48 GPIO drivers " Andy Shevchenko
2023-03-08 2:11 ` 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=20230306143309.758690-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=jay.dolan@accesio.com \
--cc=jhentges@accesio.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quarium@gmail.com \
--cc=william.gray@linaro.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 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).