Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: "Verma, Devendra" <Devendra.Verma@amd.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"mani@kernel.org" <mani@kernel.org>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Simek, Michal" <michal.simek@amd.com>
Subject: Re: [PATCH RESEND v10 2/2] dmaengine: dw-edma: Add non-LL mode
Date: Tue, 24 Feb 2026 17:27:44 -0500	[thread overview]
Message-ID: <aZ4l4IHqObEP8DfP@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <SA1PR12MB8120E7C753B717E4C8B9E7819577A@SA1PR12MB8120.namprd12.prod.outlook.com>

On Mon, Feb 23, 2026 at 04:40:07PM +0000, Verma, Devendra wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> > -----Original Message-----
> > From: Frank Li <Frank.li@nxp.com>
> > Sent: Friday, February 20, 2026 9:33 PM
> > To: Verma, Devendra <Devendra.Verma@amd.com>
> > Cc: bhelgaas@google.com; mani@kernel.org; vkoul@kernel.org;
> > dmaengine@vger.kernel.org; linux-pci@vger.kernel.org; linux-
> > kernel@vger.kernel.org; Simek, Michal <michal.simek@amd.com>
> > Subject: Re: [PATCH RESEND v10 2/2] dmaengine: dw-edma: Add non-LL
> > mode
> >
...
> > > But if it about writing a new function to check the LL mode support
> > > then I think the current variable is good enough which provides good
> > > readability and do not create any ambiguity compared to the ll region size
> > comparison.
> >
> > It is not big deal,  use 'bool cap_non_ll: 1' in dw_edma_chip. So we add more
> > cap flags in future.
> >
> > Frank
> >
>
> Hi Frank, could you elaborate what you mean by adding the cap flag? How it is going
> To help identify the overall chip state?
> I do not understand what is being implied here.

non_ll in chan means current status, which indicate one channel work at
non_ll mode or ll mode.

here dw_edma_chip means hardware's captiblity, indicate if hardware support
ll mode.

Distingiush hardware limition or current working mode.

Frank
>
> - Regards,
> Devendra
>
> > >
> > > > Frank
> > > > >
> > > > > > >
> > > > > > > > > >
> > > > > > > > > > Frank
> > > > > > > > > > >  };
> > > > > > > > > > >
> > > > > > > > > > >  /* Export to the platform drivers */
> > > > > > > > > > > --
> > > > > > > > > > > 2.43.0
> > > > > > > > > > >

  reply	other threads:[~2026-02-24 22:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 10:55 [PATCH RESEND v10 0/2] Add AMD MDB Endpoint and non-LL mode Support Devendra K Verma
2026-02-16 10:55 ` [PATCH RESEND v10 1/2] dmaengine: dw-edma: Add AMD MDB Endpoint Support Devendra K Verma
2026-02-16 19:28   ` Frank Li
2026-02-17 11:36     ` Verma, Devendra
2026-02-16 10:55 ` [PATCH RESEND v10 2/2] dmaengine: dw-edma: Add non-LL mode Devendra K Verma
2026-02-16 19:45   ` Frank Li
2026-02-17 11:48     ` Verma, Devendra
2026-02-17 16:39       ` Frank Li
2026-02-18 11:32         ` Verma, Devendra
2026-02-18 15:49           ` Frank Li
2026-02-19  9:55             ` Verma, Devendra
2026-02-19 17:07               ` Frank Li
2026-02-20 11:47                 ` Verma, Devendra
2026-02-20 16:03                   ` Frank Li
2026-02-23 16:40                     ` Verma, Devendra
2026-02-24 22:27                       ` Frank Li [this message]
2026-02-25 12:06                         ` Verma, Devendra
2026-03-02  5:55                           ` Verma, Devendra
2026-03-04 16:56                           ` Frank Li
2026-03-05 12:15                             ` Verma, Devendra
2026-03-05 16:03                               ` Frank Li
2026-03-06 11:50                                 ` Verma, Devendra
2026-03-06 18:01                                   ` Frank Li

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=aZ4l4IHqObEP8DfP@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=Devendra.Verma@amd.com \
    --cc=bhelgaas@google.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=vkoul@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