From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bhagyashri Dighole <digholebhagyashri@gmail.com>
Cc: Outreachy <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] Staging: fbtft: Replace udelay to usleep_range
Date: Sun, 3 Mar 2019 15:27:37 +0100 [thread overview]
Message-ID: <20190303142737.GA30271@kroah.com> (raw)
In-Reply-To: <CAOMPgjgN1WroEoqpDA-s1t5NVDrDJDtKCMDD=_JgAEeHh7g6dw@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Sun, Mar 03, 2019 at 07:46:55PM +0530, Bhagyashri Dighole wrote:
> Hi,
> I have gone through "Documentation/timers/timers-howto.txt", It is
> mentioned that we can put 10us-20us gap between min_range and max_range. In
> above situation `udelay(20)` our min_range is 20 and max_range is 30.
That type of delay range can be set, yes, but what are you helping here?
Also, can the hardware really support this type of longer delay? Some
hardware types can not as it is trying to rely on some sort of
semi-regular delays. Or could the delay be shorter? It's really hard
to know without knowing what the hardware is expecting and being able to
test it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-03 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 8:29 [PATCH] Staging: fbtft: Replace udelay to usleep_range Bhagyashri Dighole
2019-03-03 8:34 ` [Outreachy kernel] " Greg Kroah-Hartman
2019-03-03 14:16 ` Bhagyashri Dighole
2019-03-03 14:27 ` Greg Kroah-Hartman [this message]
2019-03-03 15:36 ` Bhagyashri Dighole
2019-03-03 16:13 ` Julia Lawall
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=20190303142737.GA30271@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=digholebhagyashri@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.