linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org,
	chris.packham@alliedtelesis.co.nz, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Darwin Dingel <darwin.dingel@alliedtelesis.co.nz>
Subject: Re: [PATCH v3 1/2] dt-bindings: serial: 8250: Add rate limit for serial port input overruns
Date: Mon, 10 Dec 2018 17:23:05 -0600	[thread overview]
Message-ID: <20181210232305.GA11474@bogus> (raw)
In-Reply-To: <20181209222739.15866-1-darwin.dingel@alliedtelesis.co.nz>

On Mon, 10 Dec 2018 11:27:39 +1300, Darwin Dingel wrote:
> When a serial port continuously experiences input overrun from
> (1) continuous receive characters from remote and or (2) hardware
> issues, its interrupt handler can preempt other tasks especially
> when the system is busy (ie. boot up period). This can cause other
> tasks to get starved of processing time from the CPU.
> 
> When this dts binding is enabled and input overrun on the serial port
> is detected, serial port receive will be throttled to give some breathing
> room for processing other tasks. Value provided will be in milliseconds.
> 
> &serial0{
> 	overrun-throttle-ms = <500>;
> };
> 
> Signed-off-by: Darwin Dingel <darwin.dingel@alliedtelesis.co.nz>
> ---
> 
> Notes:
>     Changelog
>     v1->v2:
>     - Separated dts binding to another patch
>     
>     v2->v3:
>     - Fixed commit message and reviewed-by fields
> 
>  Documentation/devicetree/bindings/serial/8250.txt | 1 +
>  1 file changed, 1 insertion(+)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

      reply	other threads:[~2018-12-10 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09 22:27 [PATCH v3 1/2] dt-bindings: serial: 8250: Add rate limit for serial port input overruns Darwin Dingel
2018-12-10 23:23 ` 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=20181210232305.GA11474@bogus \
    --to=robh@kernel.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=darwin.dingel@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).