From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753463AbbCINc0 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 9 Mar 2015 09:32:26 -0400
Received: from mga03.intel.com ([134.134.136.65]:4174 "EHLO mga03.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751931AbbCINcY (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 9 Mar 2015 09:32:24 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.11,367,1422950400"; 
   d="scan'208";a="689172774"
Message-ID: <1425907939.3838.182.camel@linux.intel.com>
Subject: Re: [RFC] With 8250 Designware UART, if writes to the LCR failed
 the kernel will hung up
From: Alan Cox <alan@linux.intel.com>
To: "long.wanglong" <long.wanglong@huawei.com>
Cc: Tim Kryger <tim.kryger@gmail.com>, Peter Hurley <peter@hurleysoftware.com>,
        Zhang Zhen <zhenzhang.zhang@huawei.com>, linux-serial@vger.kernel.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Tim Kryger <tim.kryger@linaro.org>, gregkh@linuxfoundation.org,
        jamie@jamieiles.com, arnd@arndb.de, shenjiangjiang@huawei.com,
        Wang Kai <morgan.wang@huawei.com>
Date: Mon, 09 Mar 2015 13:32:19 +0000
In-Reply-To: <54FD4779.3020902@huawei.com>
References: <54F96F5B.2090601@huawei.com>
	 <54F9DACA.3020103@hurleysoftware.com>
	 <CAD7vxxJXEz8KfXd9fBjkxTi5Nnjyw0=wwvbw5qCSwCMbBd64eA@mail.gmail.com>
	 <54FD4779.3020902@huawei.com>
Organization: Intel Corporation
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.9 (3.12.9-1.fc21) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> Maybe the next release of the board we will upgrade the serial block to the new version.
> but the issue is that how we circumvent this problem in kernel?

What is the official vendor workaround ?

Alan