From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by ozlabs.org (Postfix) with ESMTP id 4E4F467FB5 for ; Thu, 18 Aug 2005 15:48:51 +1000 (EST) Received: by zproxy.gmail.com with SMTP id i1so237421nzh for ; Wed, 17 Aug 2005 22:48:51 -0700 (PDT) Message-ID: <29495f1d0508172242734e1c99@mail.gmail.com> Date: Wed, 17 Aug 2005 22:42:36 -0700 From: Nish Aravamudan To: Kumar Gala In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: Cc: Andrew Morton , linux-kernel@vger.kernel.org, linuxppc-embedded Subject: Re: [PATCH] cpm_uart: Fix dpram allocation and non-console uarts List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 8/8/05, Kumar Gala wrote: > (A believe Marcelo would like to see this in 2.6.13, but I'll let him > fight over that ;) >=20 > * Makes dpram allocations work > * Makes non-console UART work on both 8xx and 82xx > * Fixed whitespace in files that were touched >=20 > Signed-off-by: Vitaly Bordug > Signed-off-by: Pantelis Antoniou > Signed-off-by: Kumar Gala >=20 > --- > commit 1de80554bcae877dce3b6d878053eb092ef65c72 > tree aba124824607fea1070e86501ddccc9decce362d > parent ad81111fd554c9d3c14c0a50885e076af2f9ac9b > author Kumar K. Gala Mon, 08 Aug 2005 22:35:39= -0500 > committer Kumar K. Gala Mon, 08 Aug 2005 22:35= :39 -0500 > diff --git a/drivers/serial/cpm_uart/cpm_uart_core.c b/drivers/serial/cpm= _uart/cpm_uart_core.c > --- a/drivers/serial/cpm_uart/cpm_uart_core.c > +++ b/drivers/serial/cpm_uart/cpm_uart_core.c > @@ -376,9 +396,19 @@ static int cpm_uart_startup(struct uart_ > pinfo->sccp->scc_sccm |=3D UART_SCCM_RX; > } >=20 > + if (!(pinfo->flags & FLAG_CONSOLE)) > + cpm_line_cr_cmd(line,CPM_CR_INIT_TRX); > return 0; > } >=20 > +inline void cpm_uart_wait_until_send(struct uart_cpm_port *pinfo) > +{ > + unsigned long target_jiffies =3D jiffies + pinfo->wait_closing; > + > + while (!time_after(jiffies, target_jiffies)) > + schedule(); > +} Not sure about that call here. Does the state need to be set so that you won't be run again immediately? In any case, I think direct schedule() callers are discouraged? Do you want to call a yield() or schedule_timeout({0,1}) instead maybe? > /* > * Shutdown the uart > */ > @@ -394,6 +424,12 @@ static void cpm_uart_shutdown(struct uar >=20 > /* If the port is not the console, disable Rx and Tx. */ > if (!(pinfo->flags & FLAG_CONSOLE)) { > + /* Wait for all the BDs marked sent */ > + while(!cpm_uart_tx_empty(port)) > + schedule_timeout(2); I think you are using 2 jiffies to guarantee that at least one jiffy elapses, which is fine. But, if you do not set the state beforehand, schedule_timeout() returns immediately, so you have a busy-wait here. Thanks, Nish