Received: by 2002:a17:90a:2044:0:0:0:0 with SMTP id n62csp527181pjc; Mon, 20 May 2019 11:16:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqww9Gmrdt+0BVgGErrNgPgObIV4CZcoynSmc6CQE1h8/8xgJC4fhGoNsASMYEhnAI7rBApN X-Received: by 2002:a63:1f04:: with SMTP id f4mr77434435pgf.423.1558376191755; Mon, 20 May 2019 11:16:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558376191; cv=none; d=google.com; s=arc-20160816; b=zgRPs5eBeZmw9oD8qnEgQzhIw+tpWQ+0TFZYZdG6fLYXmgT/Os9aVrhuLVukE2uCjt saFubmymPomJOC6vVHTqHm+cCVj//s+jq4zJ4RdlEqRZ3yHCjDRhWzGGbg1hlvZr0HOe LHMMw6OQvvzj9HoedNMWlDfnagY+bRfxg2z0na+IDUUkkORtIevAhEnTHAqouL1LzlzJ btp6AOkDMDj7g9XHPpk2Zjt38XUXkmEjZ9AL4G2ew/DL0K/vINdEh36bmtXPnc1qytZy 0FsgZa9icRQ8BXjjzOxvbFn82ARtvHfkG98ghI5lBaZlHmYfcUHesLPJfglqiEfWxWdn /U+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=3M5aOGI1qzRY2VLgEKYCzcXoZ/MVQvoNw6e4i8AFNJU=; b=zQoEJI7Zc2APVb9nPDsjH14AhwBjp2IqUTNQQioOwkIeGDNIQSqoPdgupAwit1so2B xyKtethK0m8g89GF92Iw3Qf4dgVIN5ja3hxxRRsxl24gajXAyZfYk9PJVzZcG/bQE9sh yi5WDzd7I3ITr8xsRn/8jIl1PGUNOENlroK+OmavE30Kaj/sWkZssfzb6/qeIUW0kw6z TKd4fv8XxQgYdUfB/Ew3g9mxoFm+xudqL6NLshi49zgoK9jf6msCewFnbL/U14of7uLl QBqF626pVAlqPKhTZ+ejPc+hQ6v4xEmWEZAg3L/Pdpc0huXOt4ePi24d28Nno4vypiwa z4EQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Y2LC56M7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j19si20181515pfd.189.2019.05.20.11.16.17; Mon, 20 May 2019 11:16:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Y2LC56M7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387917AbfETPUz (ORCPT + 99 others); Mon, 20 May 2019 11:20:55 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:55963 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389776AbfETPUw (ORCPT ); Mon, 20 May 2019 11:20:52 -0400 Received: by mail-wm1-f68.google.com with SMTP id x64so13710893wmb.5 for ; Mon, 20 May 2019 08:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=3M5aOGI1qzRY2VLgEKYCzcXoZ/MVQvoNw6e4i8AFNJU=; b=Y2LC56M7HK9juDM9pq6OI4F2G5ICKaakVBqjH4N2YgIX59hIG1aANpMi8k0QOis9b6 JjR9QWNyx8vHysLC7eGy38WvWFu2n7pW7vj1splJJijiXcTPbRaBEVqXZzXLjIeunMtY hcvmOVKvZfrdZL2MEHax7jSkLfPL2mtTz9VadkUtyVan2KtFY0XfT38N/eUHIez+z5m2 skX6mLGNbMFHpg2Pt//AvzqthbX2BskAiedo9dMmQjpnbtNNHD/2oyD0SXJO8rYK1Oet BsgOSRhRWNiQ3VfrQ3FJT4NEFK8tx7zKnoph0SHDTnSdZCTn+MlEEa8ZYo5Fbjj/EyWV QWDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3M5aOGI1qzRY2VLgEKYCzcXoZ/MVQvoNw6e4i8AFNJU=; b=CC93eP2188V53ltqkubnUGBiUkM57g4kWty804szprxctLs61OnWvdG5mF4wueV1/x qZE/46hMK8vvI6yjWElXejAsCGH8dEnAbVlZwj5kdF2EnN+zJ+x3bvmlKZrEikyte2Ay 8dU5UISPRcyF4V/GdeNba0Fw75yfycADCur+/MITx0LsXvLurXVvs/fMLiImw15d6tnF QpbUYXlnXjIv+auUZ/M/eS1EPdnjuYhXmc04qbpo0u+KweZBuW+FZgrnEil2JcjW+7tq XZy606CvFO1Ifrj3GnftUb2fvs2w2fChLbLU2dGNMyOP6RxYVMPT7/Nme6Syojt6RZYZ k4rg== X-Gm-Message-State: APjAAAWE43GfU1j7FExgPOm1Y/Mn7hH0ZhtLqrCiGWem9nmN+NsIeQlq VVgr/zxN18QvbAs7F2ec363nLw== X-Received: by 2002:a1c:a9d4:: with SMTP id s203mr10920301wme.27.1558365650358; Mon, 20 May 2019 08:20:50 -0700 (PDT) Received: from [192.168.1.7] (139.red-79-146-81.dynamicip.rima-tde.net. [79.146.81.139]) by smtp.gmail.com with ESMTPSA id f81sm16242173wmf.10.2019.05.20.08.20.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 May 2019 08:20:49 -0700 (PDT) Subject: Re: [PATCH] tty: serial: msm_serial: Fix XON/XOFF To: Bjorn Andersson Cc: Stephen Boyd , agross@kernel.org, david.brown@linaro.org, gregkh@linuxfoundation.org, jslaby@suse.com, keescook@chromium.org, anton@enomsg.org, ccross@android.com, tony.luck@intel.com, linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, khasim.mohammed@linaro.org, agsumit@qti.qualcomm.com References: <20190520103435.30850-1-jorge.ramirez-ortiz@linaro.org> <20190520145110.7BDAE21721@mail.kernel.org> <254704a2-ee20-30cd-8362-6e1bd23ec090@linaro.org> <20190520151101.GN2085@tuxbook-pro> <20190520151206.GO2085@tuxbook-pro> From: Jorge Ramirez Message-ID: <13116b66-451b-bdf9-d631-abb8ada66e01@linaro.org> Date: Mon, 20 May 2019 17:20:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20190520151206.GO2085@tuxbook-pro> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/20/19 17:12, Bjorn Andersson wrote: > On Mon 20 May 08:11 PDT 2019, Bjorn Andersson wrote: > >> On Mon 20 May 07:58 PDT 2019, Jorge Ramirez wrote: >> >>> On 5/20/19 16:56, Jorge Ramirez wrote: >>>> On 5/20/19 16:51, Stephen Boyd wrote: >>>>> Quoting Jorge Ramirez-Ortiz (2019-05-20 03:34:35) >>>>>> When the tty layer requests the uart to throttle, the current code >>>>>> executing in msm_serial will trigger "Bad mode in Error Handler" and >>>>>> generate an invalid stack frame in pstore before rebooting (that is if >>>>>> pstore is indeed configured: otherwise the user shall just notice a >>>>>> reboot with no further information dumped to the console). >>>>>> >>>>>> This patch replaces the PIO byte accessor with the word accessor >>>>>> already used in PIO mode. >>>>> >>>>> Because the hardware only accepts word based accessors and fails >>>>> otherwise? I can believe that. >>>>> >>>>> I wonder if the earlier UART hardware this driver used to support (i.e. >>>>> pre-DM) would accept byte access to the registers. It's possible, but we >>>>> don't really care because those boards aren't supported. >>>> >>>> ok. >>>> >>>> also the PIO path uses iowrite32_rep to write a number of bytes (from 1 >>>> to 4) so I think it is also appropriate to use it for XON/XOFF. >>>> >>>>> >>>>>> >>>>>> Signed-off-by: Jorge Ramirez-Ortiz >>>>>> --- >>>>> >>>>> Reviewed-by: Stephen Boyd >>>>> >>>>>> drivers/tty/serial/msm_serial.c | 5 ++++- >>>>>> 1 file changed, 4 insertions(+), 1 deletion(-) >>>>>> >>>>>> diff --git a/drivers/tty/serial/msm_serial.c b/drivers/tty/serial/msm_serial.c >>>>>> index 109096033bb1..23833ad952ba 100644 >>>>>> --- a/drivers/tty/serial/msm_serial.c >>>>>> +++ b/drivers/tty/serial/msm_serial.c >>>>>> @@ -869,10 +870,12 @@ static void msm_handle_tx(struct uart_port *port) >>>>>> else >>>>>> tf = port->membase + UART_TF; >>>>>> >>>>>> + buf[0] = port->x_char; >>>>>> + >>>>>> if (msm_port->is_uartdm) >>>>>> msm_reset_dm_count(port, 1); >>>>>> >>>>>> - iowrite8_rep(tf, &port->x_char, 1); >>>>>> + iowrite32_rep(tf, buf, 1); >>>>> >>>>> I suppose it's OK to write some extra zeroes here? >>>>> >>>>> >>>> >>>> yeah, semantically confusing msm_reset_dm_count is what really matters: >>>> it tells the hardware to only take n bytes (in this case only one) so >>>> the others will be ignored >>> >>> um after I said this, maybe iowrite32_rep should only be applied to >>> uartdm ... what do you think? >>> >> >> If I read the history correctly this write was a writel() up until >> 68252424a7c7 ("tty: serial: msm: Support big-endian CPUs"). >> >> So I think you should just change this back to a iowrite32_rep() and add >> a Fixes tag. >> > > I mean... ok. cool > > Reviewed-by: Bjorn Andersson > > Regards, > Bjorn >