From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Christopher Cordahi <christophercordahi@nanometrics.ca>
Subject: Re: [PATCH v3 3/7] memory: ti-aemif: Export aemif_*_cs_timings()
Date: Wed, 13 Nov 2024 11:55:21 +0100 [thread overview]
Message-ID: <874j4bqu7a.fsf@bootlin.com> (raw)
In-Reply-To: <20241113094938.44817-4-bastien.curutchet@bootlin.com> (Bastien Curutchet's message of "Wed, 13 Nov 2024 10:49:34 +0100")
On 13/11/2024 at 10:49:34 +01, Bastien Curutchet <bastien.curutchet@bootlin.com> wrote:
> Export the aemif_set_cs_timing() and aemif_check_cs_timing() symbols so
> they can be used by other drivers
>
> Add a mutex to protect the CS configuration register from concurrent
> accesses between the AEMIF and its 'children'.
I'll let Krzysztof judge whether it is okay to use EXPORT_SYMBOL instead
of EXPORT_SYMBOL_GPL here, but otherwise looks ok to me.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Christopher Cordahi <christophercordahi@nanometrics.ca>
Subject: Re: [PATCH v3 3/7] memory: ti-aemif: Export aemif_*_cs_timings()
Date: Wed, 13 Nov 2024 11:55:21 +0100 [thread overview]
Message-ID: <874j4bqu7a.fsf@bootlin.com> (raw)
In-Reply-To: <20241113094938.44817-4-bastien.curutchet@bootlin.com> (Bastien Curutchet's message of "Wed, 13 Nov 2024 10:49:34 +0100")
On 13/11/2024 at 10:49:34 +01, Bastien Curutchet <bastien.curutchet@bootlin.com> wrote:
> Export the aemif_set_cs_timing() and aemif_check_cs_timing() symbols so
> they can be used by other drivers
>
> Add a mutex to protect the CS configuration register from concurrent
> accesses between the AEMIF and its 'children'.
I'll let Krzysztof judge whether it is okay to use EXPORT_SYMBOL instead
of EXPORT_SYMBOL_GPL here, but otherwise looks ok to me.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
next prev parent reply other threads:[~2024-11-13 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 9:49 [PATCH v3 0/7] Implement setup_interface() in the DaVinci NAND controller Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 9:49 ` [PATCH v3 1/7] memory: ti-aemif: Create aemif_check_cs_timings() Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 10:51 ` Miquel Raynal
2024-11-13 10:51 ` Miquel Raynal
2024-11-13 9:49 ` [PATCH v3 2/7] memory: ti-aemif: Create aemif_set_cs_timings() Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 10:52 ` Miquel Raynal
2024-11-13 10:52 ` Miquel Raynal
2024-11-13 9:49 ` [PATCH v3 3/7] memory: ti-aemif: Export aemif_*_cs_timings() Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 10:55 ` Miquel Raynal [this message]
2024-11-13 10:55 ` Miquel Raynal
2024-11-13 9:49 ` [PATCH v3 4/7] mtd: rawnand: davinci: Always depends on TI_AEMIF Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 9:49 ` [PATCH v3 5/7] mtd: rawnand: davinci: Order headers alphabetically Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 9:49 ` [PATCH v3 6/7] mtd: rawnand: davinci: Add clock resource Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
2024-11-13 9:49 ` [PATCH v3 7/7] mtd: rawnand: davinci: Implement setup_interface() operation Bastien Curutchet
2024-11-13 9:49 ` Bastien Curutchet
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=874j4bqu7a.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=bastien.curutchet@bootlin.com \
--cc=christophercordahi@nanometrics.ca \
--cc=herve.codina@bootlin.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=ssantosh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.