From: Shawn Guo <shawnguo@kernel.org>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: s.hauer@pengutronix.de, festevam@gmail.com,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, system@metrotek.ru
Subject: Re: [PATCH v3] bus: imx-weim: add DT overlay support for WEIM bus
Date: Tue, 22 Feb 2022 14:55:31 +0800 [thread overview]
Message-ID: <20220222065531.GY2249@dragon> (raw)
In-Reply-To: <20220222052059.23610-1-i.bornyakov@metrotek.ru>
On Tue, Feb 22, 2022 at 08:20:59AM +0300, Ivan Bornyakov wrote:
> Add OF reconfiguration notifier handler for WEIM bus to setup Chip
> Select timings on runtime creation of child devices.
>
> However, it is not possible to load another DT overlay with conflicting
> CS timings with previously loaded overlay, even if the first one is
> unloaded. The reason is that there is no acces to CS timing property of
> a device node being removed, thus we can't track which of configured CS
> are available for re-configuration.
>
> Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
> ---
> Changelog:
> v1 -> v2: minor style fixes
> * rename "priv" -> weim_priv"
> * remove excessive newline
> v2 -> v3: minor style fixes
> * rename "weim_data *weim_priv" -> "weim_priv *priv"
>
> drivers/bus/imx-weim.c | 135 ++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 126 insertions(+), 9 deletions(-)
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-22 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 5:50 [PATCH] bus: imx-weim: add DT overlay support for WEIM bus Ivan Bornyakov
2022-02-05 5:50 ` Ivan Bornyakov
2022-02-21 7:25 ` Shawn Guo
2022-02-21 8:02 ` Ivan Bornyakov
2022-02-21 8:34 ` Shawn Guo
2022-02-21 18:29 ` [PATCH v2] " Ivan Bornyakov
2022-02-22 2:19 ` Shawn Guo
2022-02-22 5:20 ` [PATCH v3] " Ivan Bornyakov
2022-02-22 6:55 ` Shawn Guo [this message]
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=20220222065531.GY2249@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@gmail.com \
--cc=i.bornyakov@metrotek.ru \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=system@metrotek.ru \
/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).