From: Roger Quadros <rogerq@kernel.org>
To: "B. Niedermayr" <benedikt.niedermayr@siemens.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org
Cc: krzysztof.kozlowski@linaro.org, robh+dt@kernel.org, tony@atomide.com
Subject: Re: [PATCH v8 0/2] gpmc wait pin additions
Date: Fri, 28 Oct 2022 14:56:44 +0300 [thread overview]
Message-ID: <b80c95e5-6615-25b1-93b5-2db52b7d5ebe@kernel.org> (raw)
In-Reply-To: <20221021081612.591613-1-benedikt.niedermayr@siemens.com>
Hello Benedikt,
On 21/10/2022 11:16, B. Niedermayr wrote:
> From: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
>
> Currently it is not possible to configure the WAIT0PINPOLARITY and
> WAIT1PINPOLARITY bits of the GPMC_CONFIG register directly via
> device tree properties.
>
> It is also not possible to 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).
This series does not apply on v6.0 nor on v6.1-rc1.
Could you please rebase on v6.1-rc1 and send? Thanks!
cheers,
-roger
>
> Changes since v1:
> * Rebase against recent 6.0.0-rc3 kernel
> * Updated eMail recipients list
> Changes since v2:
> * Remove the gpmc register configuration out of the gpiochip
> callbacks. In this case the memory interface configuration
> is not done via gpio bindings.
> * Some minor code fixes
> * Changed git commit descriptions
> Change since v3:
> * Use a uint32 dt-property instean a boolean one
> * If the dt-property is not set, then don't touch the
> GPMC_CONFIG register
> * Changed git commit descriptions
> Changes since v4:
> * Use checkpatch with "--strict" option
> * Moved wait-pin sanity checks to gpmc_read_settings_dt()
> * Always assign WAITPINPOLARITY_DEFAULT on error cases
> * Track waitpin allocation within gpmc for determine
> allocation origin
> Changes since v5:
> * Tracking of wait-pin allocations with polarity change detection
> * Introduced a new struct gpmc_waitpin
> * Add GPMC_* to global header definitions
> * Don't allow GPMC_WAITPINPOLARITY_DEFAULT when parsing dt-properties
> * Squashed wait-pin-polarity and shared-wait-pin patches, since they
> should not be separated
> Changes since v6:
> * Move wait-pin allocation into gpmc_probe()
> * Fix s/gpmc/GPMC/ in commit description
> * use ti,wait-pin-polarity instead of gpmc,wait-pin-polarity
> * Refactored if clause in gpmc_alloc_waitpin()
> * Revert values for GPMC_WAITPINPOLARITY_ACTIVE_LOW and
> GPMC_WAITPINPOLARITY_ACTIVE_HIGH.
> Use the exact same values which are written into the register.
> Changes since v7:
> * Renamed GPMC_WAITPINPOLARITY_DEFAULT to GPMC_WAITPINPOLARITY_INVALID
> * Call gpiochip_request_own_desc() only on first wait-pin allocation
> * Fixed use of old "gpmc,wait-pin-polarity" property.
>
> Benedikt Niedermayr (2):
> memory: omap-gpmc: wait pin additions
> dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity
>
> .../memory-controllers/ti,gpmc-child.yaml | 7 +
> drivers/memory/omap-gpmc.c | 122 ++++++++++++++++--
> include/linux/platform_data/gpmc-omap.h | 8 ++
> 3 files changed, 124 insertions(+), 13 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-10-28 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 8:16 [PATCH v8 0/2] gpmc wait pin additions B. Niedermayr
2022-10-21 8:16 ` [PATCH 1/2] memory: omap-gpmc: " B. Niedermayr
2022-10-26 16:47 ` Krzysztof Kozlowski
2022-10-21 8:16 ` [PATCH 2/2] dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity B. Niedermayr
2022-10-21 14:52 ` Rob Herring
2022-10-28 11:56 ` Roger Quadros [this message]
2022-10-28 12:53 ` [PATCH v8 0/2] gpmc wait pin additions Krzysztof Kozlowski
2022-10-29 18:25 ` Roger Quadros
2022-10-29 18:26 ` Roger Quadros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b80c95e5-6615-25b1-93b5-2db52b7d5ebe@kernel.org \
--to=rogerq@kernel.org \
--cc=benedikt.niedermayr@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).