From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3F0B6ECAAD1 for ; Thu, 1 Sep 2022 12:56:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233368AbiIAM40 (ORCPT ); Thu, 1 Sep 2022 08:56:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233374AbiIAM4Z (ORCPT ); Thu, 1 Sep 2022 08:56:25 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46387844ED; Thu, 1 Sep 2022 05:56:24 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D52BD61EB5; Thu, 1 Sep 2022 12:56:23 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2C65C433D6; Thu, 1 Sep 2022 12:56:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662036983; bh=rtmOTDFsRY/njnUGoX8E3adpbd4MAljbFKCwNEpru0w=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=XhOY55ZCnokxHrwNJFuSZ6yG2FA8bt4ZyY6O6VFgSJuKmOaZpVDv7rEOhHP1B9o6f FY96TEqTOzMWvnhXAzRyWpQgZOU26OpYogr9EVEGk/x4CIyS5SP1c0sH7z48Pvr5Wj nXh/+F5xDIvloUWsIV/UZa4+RlEmy6DEoc936wOqCuz7uu3Nl94BTS4F2DauAqDcis 09GpmLwYbPbY6CPFY0FOWO+IvZNfjU3Oxy7UDLZnGz9nov6gW0gJzcViubeftEn5og AMM2Y08g8f/c6wgOOx6YUY2IfpFD4L8rtWUZDBFZT4/gJykS7aMBdCNeLCzch8Uo+n O/3OejnOSf2qQ== Message-ID: <8b166d0d-2b09-55f6-8078-c791653f3349@kernel.org> Date: Thu, 1 Sep 2022 15:56:19 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [PATCH 0/3] omap-gpmc wait pin additions Content-Language: en-US To: "B. Niedermayr" , linux-omap@vger.kernel.org, devicetree@vger.kernel.org Cc: rogerq@kernel.org, tony@atomide.com, robh+dt@kernel.org References: <20220901124144.1006238-1-benedikt.niedermayr@siemens.com> From: Krzysztof Kozlowski In-Reply-To: <20220901124144.1006238-1-benedikt.niedermayr@siemens.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 01/09/2022 15:41, B. Niedermayr wrote: > From: Benedikt Niedermayr > > There is currently no possibility for the gpmc to set either the > waitp-pin polarity or use the same wait-pin for different cs-regions. > > While the current implementation may fullfill most usecases, it may not > be sufficient for more complex setups (e.g. FPGA/ASIC interfaces), where > more complex interfacing options where possible. > > For example interfacing an ASIC which offers multiple cs-regions but > only one waitpin the current driver and dt-bindings are not sufficient. > > While using the same waitpin for different cs-regions worked for older > kernels (4.14) the omap-gpmc.c driver refused to probe (-EBUSY) with > newer kernels (>5.10). Please base your patches on a recent Linux kernel (judging by CC list this is something old) - either current RC or linux-next. Best regards, Krzysztof