[PATCH] Revert "ARM: dts: imx: move nand related property under nand at 0"

[Krzysztof Kozlowski]

On 05/03/2026 23:51, Frank Li wrote:
> On Thu, Mar 05, 2026 at 09:37:26PM +0100, Krzysztof Kozlowski wrote:
>> On 05/03/2026 21:05, Frank Li wrote:
>>> On Mon, Mar 02, 2026 at 10:49:28AM -0500, Frank Li wrote:
>>>> On Mon, Mar 02, 2026 at 11:53:00AM +0100, Max Krummenacher wrote:
>>>>> for our NAND-based modules, and our CI no longer produces any useful
>>>>> results as a consequence.
>>>>>
>>>>> I strongly believe that, as an immediate first step, the commit
>>>>> that moved the DT NAND chip configuration into its subnode should
>>>>> be reverted.
>>>>
>>>> As my previous said, can do partial revert? Just add back property under
>>>> gpmi and keep nand at 0 node.
>>>>
>>>> For example
>>>>
>>>> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-skov-cpu.dtsi
>>>> +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-skov-cpu.dtsi
>>>> @@ -260,14 +260,10 @@ fixed-link {
>>>> &gpmi {
>>>>   	pinctrl-names = "default";
>>>>   	pinctrl-0 = <&pinctrl_gpmi_nand>;
>>>> +	nand-on-flash-bbt;
>>>>   	#address-cells = <1>;
>>>>  	#size-cells = <0>;
>>>>   	status = "okay";
>>>>
>>>> Remove "- nand at 0" part.  You can use "git add -p" to do that.
>>>
>>> Do you plan rework this patch as what I said?
>>
>> Issue and revert were posted two weeks ago. That's maximum time to
>> handle regression.
> 
> Any docuement said these maxium times, I also want to know other maximum

Just read the regression and bug handling docs in the kernel.

> time, such as
> 	what's max time maintainer need reply? Many patch is not any
> reponse for long time.




Best regards,
Krzysztof