From: Greg KH <gregkh@linuxfoundation.org>
To: Tharunkumar.Pasumarthi@microchip.com
Cc: Kumaravel.Thiagarajan@microchip.com, arnd@arndb.de,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
UNGLinuxDriver@microchip.com, lkp@intel.com
Subject: Re: [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch
Date: Mon, 6 Feb 2023 10:41:43 +0100 [thread overview]
Message-ID: <Y+DLVwfOjEKYJpyB@kroah.com> (raw)
In-Reply-To: <PH7PR11MB59587A0639FE44245A68312B9BDA9@PH7PR11MB5958.namprd11.prod.outlook.com>
On Mon, Feb 06, 2023 at 09:20:51AM +0000, Tharunkumar.Pasumarthi@microchip.com wrote:
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Friday, January 20, 2023 4:26 PM
> > To: Kumaravel Thiagarajan - I21417
> > <Kumaravel.Thiagarajan@microchip.com>
> > > + dev_err(&priv->pdev->dev,
> > > + "EPC_Timeout, EEPROM is unresponsive: %x\n",
> > > + data);
> >
> > Can this spam the kernel logs? If so, please rate limit it.
>
> This print will only come once at max and will not spam logs.
>
> > > + delay = msecs_to_jiffies(OTP_RW_TIMEOUT_MILLISECONDS);
> > > + j0 = jiffies;
> > > + j1 = j0 + delay;
> >
> > Are you sure this math works out? Please use the jiffies math functions
> > instead so you can handle wrapping properly.
>
> You suggest using any existing APIs to add jiffies to handle wrapping? I am not able
> to find any such API. Can you please point out API name.
I have no context here for what you are doing with the math in jiffies,
but that is usually a very odd thing. If you use the normal timer
functions, you will not have to worry about the wrapping as it is
handled for you, right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-06 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 19:29 [PATCH v3 char-misc-next] misc: microchip: pci1xxxx: Add OTP/EEPROM driver for the pci1xxxx switch Kumaravel Thiagarajan
2023-01-20 10:55 ` Greg KH
2023-02-06 9:20 ` Tharunkumar.Pasumarthi
2023-02-06 9:41 ` Greg KH [this message]
2023-02-06 17:03 ` Tharunkumar.Pasumarthi
2023-02-06 17:48 ` Greg KH
2023-02-07 9:52 ` Tharunkumar.Pasumarthi
2023-02-07 10:34 ` Tharunkumar.Pasumarthi
2023-02-08 11:56 ` Greg KH
2023-02-07 13:45 ` Michael Walle
2023-02-08 6:43 ` Tharunkumar.Pasumarthi
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=Y+DLVwfOjEKYJpyB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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