All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Rabara, Niravkumar L" <niravkumar.l.rabara@intel.com>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 "linux@treblig.org" <linux@treblig.org>,
	 Shen Lichuan <shenlichuan@vivo.com>,
	 Jinjie Ruan <ruanjinjie@huawei.com>,
	"u.kleine-koenig@baylibre.com" <u.kleine-koenig@baylibre.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] mtd: rawnand: cadence: support deferred prob when DMA is not ready
Date: Tue, 04 Feb 2025 10:20:17 +0100	[thread overview]
Message-ID: <87o6zi83se.fsf@bootlin.com> (raw)
In-Reply-To: <BL3PR11MB6532451B44E7C5D82F5EC4AFA2F42@BL3PR11MB6532.namprd11.prod.outlook.com> (Niravkumar L. Rabara's message of "Tue, 4 Feb 2025 07:48:57 +0000")

Hello,

> My apologies for the confusion.
> Slave DMA terminology used in cadence nand controller bindings and
> driver is indeed confusing.  
>
> To answer your question it is, 
> 1 - External DMA (Generic DMA controller).
>
> Nand controller IP do not have embedded DMA controller (2 - peripheral DMA). 
>
> FYR, how external DMA is used. 
> https://elixir.bootlin.com/linux/v6.13.1/source/drivers/mtd/nand/raw/cadence-nand-controller.c#L1962

In this case we should have a dmas property (and perhaps dma-names), no?

Miquèl

______________________________________________________
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: "Rabara, Niravkumar L" <niravkumar.l.rabara@intel.com>
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 "linux@treblig.org" <linux@treblig.org>,
	 Shen Lichuan <shenlichuan@vivo.com>,
	 Jinjie Ruan <ruanjinjie@huawei.com>,
	"u.kleine-koenig@baylibre.com" <u.kleine-koenig@baylibre.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] mtd: rawnand: cadence: support deferred prob when DMA is not ready
Date: Tue, 04 Feb 2025 10:20:17 +0100	[thread overview]
Message-ID: <87o6zi83se.fsf@bootlin.com> (raw)
In-Reply-To: <BL3PR11MB6532451B44E7C5D82F5EC4AFA2F42@BL3PR11MB6532.namprd11.prod.outlook.com> (Niravkumar L. Rabara's message of "Tue, 4 Feb 2025 07:48:57 +0000")

Hello,

> My apologies for the confusion.
> Slave DMA terminology used in cadence nand controller bindings and
> driver is indeed confusing.  
>
> To answer your question it is, 
> 1 - External DMA (Generic DMA controller).
>
> Nand controller IP do not have embedded DMA controller (2 - peripheral DMA). 
>
> FYR, how external DMA is used. 
> https://elixir.bootlin.com/linux/v6.13.1/source/drivers/mtd/nand/raw/cadence-nand-controller.c#L1962

In this case we should have a dmas property (and perhaps dma-names), no?

Miquèl

  reply	other threads:[~2025-02-04  9:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  3:21 [PATCH v2 0/3] mtd: rawnand: cadence: improvement and fixes niravkumar.l.rabara
2025-01-16  3:21 ` niravkumar.l.rabara
2025-01-16  3:21 ` [PATCH v2 1/3] mtd: rawnand: cadence: support deferred prob when DMA is not ready niravkumar.l.rabara
2025-01-16  3:21   ` niravkumar.l.rabara
2025-01-21  9:52   ` Miquel Raynal
2025-01-21  9:52     ` Miquel Raynal
2025-01-29  9:17     ` Rabara, Niravkumar L
2025-01-29  9:17       ` Rabara, Niravkumar L
2025-01-29 10:02       ` Miquel Raynal
2025-01-29 10:02         ` Miquel Raynal
2025-01-30  3:51         ` Rabara, Niravkumar L
2025-01-30  3:51           ` Rabara, Niravkumar L
2025-01-30 15:19           ` Miquel Raynal
2025-01-30 15:19             ` Miquel Raynal
2025-02-04  7:48             ` Rabara, Niravkumar L
2025-02-04  7:48               ` Rabara, Niravkumar L
2025-02-04  9:20               ` Miquel Raynal [this message]
2025-02-04  9:20                 ` Miquel Raynal
2025-02-04 10:43                 ` Rabara, Niravkumar L
2025-02-04 10:43                   ` Rabara, Niravkumar L
2025-02-04 13:32                   ` Miquel Raynal
2025-02-04 13:32                     ` Miquel Raynal
2025-02-04 14:11                     ` Rabara, Niravkumar L
2025-02-04 14:11                       ` Rabara, Niravkumar L
2025-02-06 17:01                       ` Miquel Raynal
2025-02-06 17:01                         ` Miquel Raynal
2025-02-07  9:12                         ` Rabara, Niravkumar L
2025-02-07  9:12                           ` Rabara, Niravkumar L
2025-02-07 13:22                           ` Miquel Raynal
2025-02-07 13:22                             ` Miquel Raynal
2025-01-16  3:21 ` [PATCH v2 2/3] mtd: rawnand: cadence: use dma_map_resource for sdma address niravkumar.l.rabara
2025-01-16  3:21   ` niravkumar.l.rabara
2025-01-21  9:53   ` Miquel Raynal
2025-01-21  9:53     ` Miquel Raynal
2025-01-29  9:02     ` Rabara, Niravkumar L
2025-01-29  9:02       ` Rabara, Niravkumar L
2025-01-29  9:50       ` Miquel Raynal
2025-01-29  9:50         ` Miquel Raynal
2025-01-16  3:21 ` [PATCH v2 3/3] mtd: rawnand: cadence: fix incorrect dev context in dma_unmap_single niravkumar.l.rabara
2025-01-16  3:21   ` niravkumar.l.rabara
2025-01-21  9:54   ` Miquel Raynal
2025-01-21  9:54     ` Miquel Raynal
2025-01-29  8:58     ` Rabara, Niravkumar L
2025-01-29  8:58       ` Rabara, Niravkumar L
2025-01-29  9:48       ` Miquel Raynal
2025-01-29  9:48         ` Miquel Raynal

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=87o6zi83se.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@treblig.org \
    --cc=niravkumar.l.rabara@intel.com \
    --cc=richard@nod.at \
    --cc=ruanjinjie@huawei.com \
    --cc=shenlichuan@vivo.com \
    --cc=stable@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.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.