Linux Input/HID development
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] Input: tsc2007 - Read "ti,poll-period" as u32
Date: Mon, 31 Aug 2026 18:18:29 -0500	[thread overview]
Message-ID: <20260831231829.GA1244140-robh@kernel.org> (raw)
In-Reply-To: <apXaYJhFnC0UCHb0@google.com>

On Mon, Aug 31, 2026 at 12:51:44PM -0700, Dmitry Torokhov wrote:
> Hi Rob,
> 
> On Mon, Aug 31, 2026 at 02:43:51PM -0500, Rob Herring (Arm) wrote:
> > The "ti,poll-period" property is documented as a normal uint32 cell.
> > The driver used a u64 helper, which makes the helper type disagree with
> > the schema even though the stored value is still small.
> > 
> > Read "ti,poll-period" with the u32 helper matching the documented DT
> > cell size.
> > 
> > Assisted-by: Codex:gpt-5-5
> > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> > ---
> >  drivers/input/touchscreen/tsc2007_core.c | 5 ++---
> >  1 file changed, 2 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/input/touchscreen/tsc2007_core.c b/drivers/input/touchscreen/tsc2007_core.c
> > index e4d7da0f4434..e2f49b37e18c 100644
> > --- a/drivers/input/touchscreen/tsc2007_core.c
> > +++ b/drivers/input/touchscreen/tsc2007_core.c
> > @@ -221,7 +221,6 @@ static int tsc2007_get_pendown_state_gpio(struct device *dev)
> >  static int tsc2007_probe_properties(struct device *dev, struct tsc2007 *ts)
> >  {
> >  	u32 val32;
> > -	u64 val64;
> >  
> >  	if (!device_property_read_u32(dev, "ti,max-rt", &val32))
> >  		ts->max_rt = val32;
> > @@ -237,8 +236,8 @@ static int tsc2007_probe_properties(struct device *dev, struct tsc2007 *ts)
> >  	if (!device_property_read_u32(dev, "ti,fuzzz", &val32))
> >  		ts->fuzzz = val32;
> >  
> > -	if (!device_property_read_u64(dev, "ti,poll-period", &val64))
> > -		ts->poll_period = msecs_to_jiffies(val64);
> > +	if (!device_property_read_u32(dev, "ti,poll-period", &val32))
> 
> Do we need to handle -EOVERFLOW and keep compatibility with device trees
> that used /64/ to match driver implementation? Or we expect that there
> were/are none?

I suspect there aren't any users. Nothing upstream for sure and there 
never was. We could probably just delete the property.

Rob

      reply	other threads:[~2026-08-31 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 19:43 [RESEND PATCH] Input: tsc2007 - Read "ti,poll-period" as u32 Rob Herring (Arm)
2026-08-31 19:51 ` Dmitry Torokhov
2026-08-31 23:18   ` Rob Herring [this message]

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=20260831231829.GA1244140-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox