All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
	 Pratyush Yadav <pratyush@kernel.org>,
	 Michael Walle <mwalle@kernel.org>,
	linux-kernel@vger.kernel.org,  linux-mtd@lists.infradead.org
Subject: Re: [PATCH] memory: fsl_ifc: Make FSL_IFC config visible and selectable
Date: Thu, 23 May 2024 16:32:01 +0200	[thread overview]
Message-ID: <87cypc38gu.fsf@geanix.com> (raw)
In-Reply-To: <979fd913-050b-445d-9ca8-0ec6906ce3ea@kernel.org> (Krzysztof Kozlowski's message of "Thu, 23 May 2024 16:01:49 +0200")

Krzysztof Kozlowski <krzk@kernel.org> writes:

> On 23/05/2024 15:58, Esben Haabendal wrote:
>> While use of fsl_ifc driver with NAND flash is fine, as the fsl_ifc_nand
>> driver selects FSL_IFC automatically, we need the option to be selectable
>> for platforms using fsl_ifc with NOR flash.
>
> Which driver is that?

This is drivers/memory/fsl_ifc.o driver. It is for Integrated Flash
Controller (IFC) from NXP. It is used in various Layerscape socs.

> Which DTS?

It is for "fsl,ifc" compatible devices.

/Esben

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Esben Haabendal <esben@geanix.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
	 Pratyush Yadav <pratyush@kernel.org>,
	 Michael Walle <mwalle@kernel.org>,
	linux-kernel@vger.kernel.org,  linux-mtd@lists.infradead.org
Subject: Re: [PATCH] memory: fsl_ifc: Make FSL_IFC config visible and selectable
Date: Thu, 23 May 2024 16:32:01 +0200	[thread overview]
Message-ID: <87cypc38gu.fsf@geanix.com> (raw)
In-Reply-To: <979fd913-050b-445d-9ca8-0ec6906ce3ea@kernel.org> (Krzysztof Kozlowski's message of "Thu, 23 May 2024 16:01:49 +0200")

Krzysztof Kozlowski <krzk@kernel.org> writes:

> On 23/05/2024 15:58, Esben Haabendal wrote:
>> While use of fsl_ifc driver with NAND flash is fine, as the fsl_ifc_nand
>> driver selects FSL_IFC automatically, we need the option to be selectable
>> for platforms using fsl_ifc with NOR flash.
>
> Which driver is that?

This is drivers/memory/fsl_ifc.o driver. It is for Integrated Flash
Controller (IFC) from NXP. It is used in various Layerscape socs.

> Which DTS?

It is for "fsl,ifc" compatible devices.

/Esben

  reply	other threads:[~2024-05-23 14:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 13:58 [PATCH] memory: fsl_ifc: Make FSL_IFC config visible and selectable Esben Haabendal
2024-05-23 13:58 ` Esben Haabendal
2024-05-23 14:01 ` Krzysztof Kozlowski
2024-05-23 14:01   ` Krzysztof Kozlowski
2024-05-23 14:32   ` Esben Haabendal [this message]
2024-05-23 14:32     ` Esben Haabendal
2024-05-23 14:36     ` Krzysztof Kozlowski
2024-05-23 14:36       ` Krzysztof Kozlowski
2024-05-24  8:47       ` Esben Haabendal
2024-05-24  8:47         ` Esben Haabendal
2024-05-25 16:41         ` Krzysztof Kozlowski
2024-05-25 16:41           ` Krzysztof Kozlowski
2024-05-27  6:55           ` Esben Haabendal
2024-05-27  6:55             ` Esben Haabendal
2024-05-27  7:19             ` Krzysztof Kozlowski
2024-05-27  7:19               ` Krzysztof Kozlowski
2024-05-27  7:35               ` Esben Haabendal
2024-05-27  7:35                 ` Esben Haabendal
2024-05-27  7:47                 ` Esben Haabendal
2024-05-27  7:47                   ` Esben Haabendal
2024-05-28  6:53                   ` Krzysztof Kozlowski
2024-05-28  6:53                     ` Krzysztof Kozlowski
2024-05-28 10:03                     ` Esben Haabendal
2024-05-28 10:03                       ` Esben Haabendal
2024-05-28 10:21                       ` Krzysztof Kozlowski
2024-05-28 10:21                         ` Krzysztof Kozlowski
2024-05-28 11:01                         ` Esben Haabendal
2024-05-28 11:01                           ` Esben Haabendal

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=87cypc38gu.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=tudor.ambarus@linaro.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 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.