From: Christophe Kerello <christophe.kerello@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 3/5] memory: stm32-fmc2-ebi: add MP25 support
Date: Mon, 26 Feb 2024 09:26:31 +0100 [thread overview]
Message-ID: <9fb17963-8942-4810-ae86-508fd7b3466a@foss.st.com> (raw)
In-Reply-To: <21ad2752-ad25-451a-b892-6b3b31c1031a@linaro.org>
Hi Krzysztof,
On 2/21/24 09:32, Krzysztof Kozlowski wrote:
> On 19/02/2024 15:02, Christophe Kerello wrote:
>> Add the support of the revision 2 of FMC2 IP.
>> - PCSCNTR register has been removed,
>> - CFGR register has been added,
>> - the bit used to enable the IP has moved from BCR1 to CFGR,
>> - the timeout for CEx deassertion has moved from PCSCNTR to BCRx,
>> - the continuous clock enable has moved from BCR1 to CFGR,
>> - the clk divide ratio has moved from BCR1 to CFGR.
>>
>> The MP1 SoCs have only one signal to manage all the controllers (NWAIT).
>> The MP25 SOC has one RNB signal for the NAND controller and one NWAIT
>> signal for the memory controller.
>>
>> Let's use a platform data structure for parameters that will differ
>> between MP1 and MP25.
>
>
> ...
>
>> +
>> ebi->regmap = device_node_to_regmap(dev->of_node);
>> if (IS_ERR(ebi->regmap))
>> return PTR_ERR(ebi->regmap);
>> @@ -1190,9 +1502,11 @@ static int stm32_fmc2_ebi_probe(struct platform_device *pdev)
>> if (ret)
>> goto err_release;
>>
>> - ret = stm32_fmc2_ebi_save_setup(ebi);
>> - if (ret)
>> - goto err_release;
>> + if (ebi->data->save_setup) {
>
> This cannot be NULL.
Ok, it will be done in V3.
Regards,
Christophe Kerello.
>
>> + ret = ebi->data->save_setup(ebi);
>> + if (ret)
>> + goto err_release;
>> + }
>>
>> platform_set_drvdata(pdev, ebi);
>>
>> @@ -1238,7 +1552,9 @@ static int __maybe_unused stm32_fmc2_ebi_resume(struct device *dev)
>> if (ret)
>> return ret;
>>
>> - stm32_fmc2_ebi_set_setup(ebi);
>> + if (ebi->data->set_setup)
>
> This cannot be NULL.
>
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-02-26 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:01 [PATCH v2 0/5] memory: stm32-fmc2-ebi: Add MP25 FMC2 support Christophe Kerello
2024-02-19 14:01 ` [PATCH v2 1/5] dt-bindings: memory-controller: st,stm32: add MP25 support Christophe Kerello
2024-02-20 9:56 ` Krzysztof Kozlowski
2024-02-21 8:27 ` Krzysztof Kozlowski
2024-02-19 14:01 ` [PATCH v2 2/5] memory: stm32-fmc2-ebi: check regmap_read return value Christophe Kerello
2024-02-21 8:29 ` Krzysztof Kozlowski
2024-02-26 8:25 ` Christophe Kerello
2024-02-19 14:02 ` [PATCH v2 3/5] memory: stm32-fmc2-ebi: add MP25 support Christophe Kerello
2024-02-21 8:32 ` Krzysztof Kozlowski
2024-02-26 8:26 ` Christophe Kerello [this message]
2024-02-19 14:02 ` [PATCH v2 4/5] memory: stm32-fmc2-ebi: add MP25 RIF support Christophe Kerello
2024-02-19 14:02 ` [PATCH v2 5/5] memory: stm32-fmc2-ebi: keep power domain on Christophe Kerello
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=9fb17963-8942-4810-ae86-508fd7b3466a@foss.st.com \
--to=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®