From: Rob Herring <robh@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: alistair@alistair23.me, alistair23@gmail.com,
andreas@kemnade.info, devicetree@vger.kernel.org,
dmitry.torokhov@gmail.com, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
maxime.ripard@bootlin.com, mylene.josserand@bootlin.com,
rydberg@bitmath.org
Subject: Re: [PATCH v5 1/4] Input: Add driver for Cypress Generation 5 touchscreen
Date: Fri, 21 Jan 2022 16:43:06 -0600 [thread overview]
Message-ID: <Yes2+ps8qTT52g3Z@robh.at.kernel.org> (raw)
In-Reply-To: <20220119012637.1713748-1-pgwipeout@gmail.com>
On Tue, Jan 18, 2022 at 08:26:37PM -0500, Peter Geis wrote:
> Good Evening,
>
> I tried using this with a cypress tma448 and thought there was an issue
> with the driver.
> Further investigation found the tma448 in question had no configuration
> burned into it, thus max size and pressure are zero.
>
> I've added the patch below to extend the driver with device tree
> overrides.
> Unfortunately device_property_read_u16 is broken on arm64 currently, as
> it returns zero.
FYI, I replied to your bug report:
https://lore.kernel.org/all/CAMdYzYquceSBrOsvO8rW9wmJA_RO=HSwv_waVoS=0hsP414T-A@mail.gmail.com/
Rob
next prev parent reply other threads:[~2022-01-21 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 11:53 [PATCH v5 0/4] Add support for the Cypress cyttsp5 Alistair Francis
2022-01-09 11:53 ` [PATCH v5 1/4] Input: Add driver for Cypress Generation 5 touchscreen Alistair Francis
2022-01-19 1:26 ` Peter Geis
2022-01-21 22:43 ` Rob Herring [this message]
2022-01-09 11:53 ` [PATCH v5 2/4] dt-bindings: input: Add Cypress TT2100 touchscreen controller Alistair Francis
2022-01-16 0:34 ` Linus Walleij
2022-01-21 22:08 ` Rob Herring
2022-01-09 11:53 ` [PATCH v5 3/4] ARM: imx_v6_v7_defconfig: Enable the cyttsp5 touchscreen Alistair Francis
2022-01-09 11:53 ` [PATCH v5 4/4] ARM: dts: imx7d-remarkable2: Enable the cyttsp5 Alistair Francis
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=Yes2+ps8qTT52g3Z@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mylene.josserand@bootlin.com \
--cc=pgwipeout@gmail.com \
--cc=rydberg@bitmath.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).