From: Krzysztof Kozlowski <krzk@kernel.org>
To: "B. Niedermayr" <benedikt.niedermayr@siemens.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Cc: rogerq@kernel.org, tony@atomide.com, robh+dt@kernel.org
Subject: Re: [PATCH v2 0/3] omap-gpmc wait pin additions
Date: Mon, 5 Sep 2022 09:44:03 +0300 [thread overview]
Message-ID: <9d5182cc-2c2f-287d-b1d4-a4f5fb19788b@kernel.org> (raw)
In-Reply-To: <20220902091028.1346952-1-benedikt.niedermayr@siemens.com>
On 02/09/2022 12:10, B. Niedermayr wrote:
> From: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
>
> 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).
>
> Changes since v1:
> * Rebase against recent 6.0.0-rc3 kernel, but the maintainers list
> stays the same!
No... thanks for rebasing yet still you use wrong address email.
>
> ./scripts/get_maintainer.pl drivers/memory/omap-gpmc.c
> Roger Quadros <rogerq@kernel.org> (maintainer:OMAP GENERAL PURPOSE MEMORY CONTROLLER SUPPORT)
> Tony Lindgren <tony@atomide.com> (maintainer:OMAP GENERAL PURPOSE MEMORY CONTROLLER SUPPORT)
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> (maintainer:MEMORY CONTROLLER DRIVERS)
Different address email.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-05 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 9:10 [PATCH v2 0/3] omap-gpmc wait pin additions B. Niedermayr
2022-09-02 9:10 ` [PATCH v2 1/3] memory: omap-gpmc: allow shared wait pins B. Niedermayr
2022-09-02 9:10 ` [PATCH v2 2/3] memory: omap-gpmc: add support for wait pin polarity B. Niedermayr
2022-09-02 9:10 ` [PATCH v2 3/3] dt-bindings: memory-controllers: gpmc-child: Add binding for wait-pin-polarity B. Niedermayr
2022-09-05 6:44 ` Krzysztof Kozlowski [this message]
2022-09-05 7:15 ` [PATCH v2 0/3] omap-gpmc wait pin additions Niedermayr, BENEDIKT
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 7:17 B. Niedermayr
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=9d5182cc-2c2f-287d-b1d4-a4f5fb19788b@kernel.org \
--to=krzk@kernel.org \
--cc=benedikt.niedermayr@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@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).