From: Vincent Jardin <vjardin@free.fr>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Laurentiu Tudor <laurentiu.tudor@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bogdan Purcareata <bogdan.purcareata@nxp.com>,
Stuart Yoder <stuyoder@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] bus: fsl-mc: set dma_mask for the root DPRC device
Date: Fri, 31 Jul 2026 20:47:09 +0200 [thread overview]
Message-ID: <amztrR-CAHlMN49T@L30177.local> (raw)
In-Reply-To: <smvzffc65xr23fyozcahv4ifj643hxd6rj6uu6pi6ikc2tfvqx@ik4vkhhjytxh>
Hi Ioana,
> > Fixes: a259ed1618d2 ("bus/fsl-mc: support dma configure for devices on fsl-mc bus")
>
> Is this fixing an actual bug introduced by the blamed commit or are we
> talking only about the warning message?
It is just a warning message.
I did more test today. I reverted it on my LX2160A with the SMMU-less config and rebooted.
Then, I get this notification:
dprc.1: DMA mask not set
Still the DPRC binds, all DPAA2 children (dpni/dpio/dpbp) probe.
In practice, it is more a cleanup warning/notification. I do not remember why I did state
this commit log that is few month old.
I'll rework the v2 per your suggested common block, I'll drop Cc: stable and update
my commit log accordingly.
Best regards,
Vincent
> Commit 4d8bde883bfb ("OF: Don't set default coherent DMA mask") is the
> one that added the dev_warn.
prev parent reply other threads:[~2026-07-31 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 22:56 [PATCH] bus: fsl-mc: set dma_mask for the root DPRC device Vincent Jardin via B4 Relay
2026-07-30 15:39 ` Ioana Ciornei
2026-07-31 18:47 ` Vincent Jardin [this message]
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=amztrR-CAHlMN49T@L30177.local \
--to=vjardin@free.fr \
--cc=bogdan.purcareata@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org \
--cc=stuyoder@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox