Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp738488ybi; Fri, 14 Jun 2019 02:31:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqz7CJCrgIPAAcp/Khzt80pKgJkQ6n+b+Zb7yKMe8NDah9E1vaMDdaZ0FAH61HZS4wU0FXTU X-Received: by 2002:a17:90a:8985:: with SMTP id v5mr9939752pjn.136.1560504662078; Fri, 14 Jun 2019 02:31:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560504662; cv=none; d=google.com; s=arc-20160816; b=Ymqo/nNL5ETHtvPXoGRKkXjdzWSx5uHeN59FSjfswsjuiErXgXnf6zkMS9jro/jeSQ abPr1vLelzxh8O616ywNvbAgoM74IsavqNDJn/FOvHOZIfSnHHupDWQXMPoyVrkQSfFz JOQAqzuMKPx7/9rUKuAvL0d0MASrotVBvJ5USz5L/se5MllzKL1O6DLxrLRRGaq6Sx2B XfzkacsvI1VPUDY1jP75tqUU+w3pneadUKMY7zA4ggs8JsdAwKyKYZ1JMqQ4lece5YzI 8uiI8s7WsGnOj0O0gaPxj5GD8ULMbEjxqEywLBeNtivnfLmsso12C9ShR1jKb15sdo/J PdfA== 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:date:message-id:from :references:cc:to:subject; bh=ZYxSsImaWSI1c5sj/fFRoi5HLH+9kHdE5lwceB8TRNI=; b=dWKMVQ3E8cdHRtxbPZnkTuN5jQU+qz/gftDgD56i+YO2JNUN4H6k7AUWO/eL8VyMA9 vfWD/ahDJ5rEG6sDAw9fVBxUw04HbrHur6gaLH9Z/Blov2PtO8XbWmISkGkRY5l5TZIo 4FbmPlaqxL4j/hE9Pzldx/BMt/L8dYX8imGsauYNLXirqDdF9c6gPKrFNCYBlyrtgWF6 yf10VRJvgplG1TYHf2H/lvBmy/q7qrkzOnKTS2YJiKAY708Q0ezvbgU3ui64Y9tcy8r4 YG8zSRuQQNIG2VtpqKNgSmHO1BcXb0jSX8soxwq7/utZUCFqRsl9is6LwWf2zx6rEIDF FYHw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 13si2041291pgk.239.2019.06.14.02.30.44; Fri, 14 Jun 2019 02:31:02 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726995AbfFNJ3j (ORCPT + 99 others); Fri, 14 Jun 2019 05:29:39 -0400 Received: from mx2.mailbox.org ([80.241.60.215]:35582 "EHLO mx2.mailbox.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726479AbfFNJ3j (ORCPT ); Fri, 14 Jun 2019 05:29:39 -0400 Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 8DF5FA1091; Fri, 14 Jun 2019 11:29:35 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id yKkjF9F1R2O0; Fri, 14 Jun 2019 11:29:31 +0200 (CEST) Subject: Re: [PATCH 1/3 v6] serial: mctrl_gpio: Check if GPIO property exisits before requesting it To: Yegor Yefremov , Andy Shevchenko Cc: linux-serial@vger.kernel.org, kernel list , Mika Westerberg , Greg Kroah-Hartman , Giulio Benetti References: <20190613154542.32438-1-sr@denx.de> <20190613170802.GE9224@smile.fi.intel.com> From: Stefan Roese Message-ID: <0bf6629c-cedf-e1dd-b42b-989c6711d390@denx.de> Date: Fri, 14 Jun 2019 11:29:29 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed 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 14.06.19 11:04, Yegor Yefremov wrote: > On Thu, Jun 13, 2019 at 7:08 PM Andy Shevchenko > wrote: >> >> On Thu, Jun 13, 2019 at 05:45:40PM +0200, Stefan Roese wrote: >>> This patch adds a check for the GPIOs property existence, before the >>> GPIO is requested. This fixes an issue seen when the 8250 mctrl_gpio >>> support is added (2nd patch in this patch series) on x86 platforms using >>> ACPI. >>> >>> Here Mika's comments from 2016-08-09: >>> >>> " >>> I noticed that with v4.8-rc1 serial console of some of our Broxton >>> systems does not work properly anymore. I'm able to see output but input >>> does not work. >>> >>> I bisected it down to commit 4ef03d328769eddbfeca1f1c958fdb181a69c341 >>> ("tty/serial/8250: use mctrl_gpio helpers"). >>> >>> The reason why it fails is that in ACPI we do not have names for GPIOs >>> (except when _DSD is used) so we use the "idx" to index into _CRS GPIO >>> resources. Now mctrl_gpio_init_noauto() goes through a list of GPIOs >>> calling devm_gpiod_get_index_optional() passing "idx" of 0 for each. The >>> UART device in Broxton has following (simplified) ACPI description: >>> >>> Device (URT4) >>> { >>> ... >>> Name (_CRS, ResourceTemplate () { >>> GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly, >>> "\\_SB.GPO0", 0x00, ResourceConsumer) >>> { >>> 0x003A >>> } >>> GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly, >>> "\\_SB.GPO0", 0x00, ResourceConsumer) >>> { >>> 0x003D >>> } >>> }) >>> >>> In this case it finds the first GPIO (0x003A which happens to be RX pin >>> for that UART), turns it into GPIO which then breaks input for the UART >>> device. This also breaks systems with bluetooth connected to UART (those >>> typically have some GPIOs in their _CRS). >>> >>> Any ideas how to fix this? >>> >>> We cannot just drop the _CRS index lookup fallback because that would >>> break many existing machines out there so maybe we can limit this to >>> only DT enabled machines. Or alternatively probe if the property first >>> exists before trying to acquire the GPIOs (using >>> device_property_present()). >>> " >>> >>> This patch implements the fix suggested by Mika in his statement above. >>> >> >> Reviewed-by: Andy Shevchenko > > I cannot compile the driver without adding #include > to drivers/tty/serial/serial_mctrl_gpio.c. > > My platform is AM335X (OMAP3). I've tried the patches both against the > main repo and also tty-next. > > Other than that everything is working. Thanks for reporting. I'll wait a bit for other review comments and tests (thanks Andy) and will then send v7 with this header included (and compile tested on OMAP3) later next week. BTW: Could you please add a Tested-by-tag with the next version? Thanks, Stefan