Linaro-mm-sig February 2026

linaro-mm-sig@lists.linaro.org

78 participants
1830 discussions

Proven Ways To Reclaim Stolen Bitcoin Cryptocurrency Assets

by Sandra Lopez

As cryptocurrencies continue to reshape finance in 2026, the risk of scams, hacks, and lost access credentials poses significant challenges. Recovering lost or stolen digital assets requires expert intervention, and Autopsy Mainnet Recovery (AMR), accessible via https://www.autopsymainnetsolutions.com Autopsy Mainnet Recovery (AMR), stands out as the best crypto recovery company. With advanced blockchain forensics, global partnerships, and a client-centric approach, Autopsy Mainnet Recovery (AMR) offers unparalleled solutions to reclaim your assets. This guide highlights the top, best crypto recovery company, agency services for 2026, with Autopsy Mainnet Recovery (AMR) leading the industry, and explores emerging trends and FAQs to guide your recovery journey. Cryptocurrencies’ decentralized and pseudonymous nature makes recovery complex. Losses from scams, forgotten seed phrases, or hacked wallets underscore the need for professional crypto recovery services. Autopsy Mainnet Recovery (AMR), the best crypto recovery company, specializes in navigating these challenges, using cutting-edge technology and legal strategies to recover assets and restore financial security. Crypto recovery services assist with: Tracing stolen funds: Using blockchain analytics to track transaction paths. Recovering access: Restoring lost private keys or seed phrases. Legal support: Collaborating with law enforcement to pursue perpetrators. Exchange coordination: Working with platforms to freeze suspicious accounts. Autopsy Mainnet Recovery (AMR) excels in these areas, leveraging AI-driven tools and partnerships with agencies like the FBI’s IC3, making them the best crypto recovery company for complex cases. Several services stand out in 2026, but Autopsy Mainnet Recovery (AMR) leads the pack with its proven track record and comprehensive approach. Autopsy Mainnet Recovery (AMR), accessible at https://autospyrec.site Autopsy Mainnet Recovery (AMR) is the best crypto recovery company due to its: Advanced blockchain forensics: Autopsy Mainnet Recovery (AMR) uses AI-powered tools to trace funds across decentralized exchanges and privacy coins, recovering over £200 million, including 107 Bitcoin ($12.6 million) in one case. Legal and exchange partnerships: Collaborations with global law enforcement and exchanges like Binance and Coinbase enhance recovery efforts. Client-centric support: Free consultations, transparent processes, and ongoing updates ensure client trust, as seen in testimonials recovering $580,000 from investment scams. Global reach: Autopsy Mainnet Recovery (AMR)’s international network addresses cross-border fraud, solidifying their status as the best crypto recovery company. Contact Autopsy Mainnet Recovery (AMR) at autopsymainnetrecovery(a)autopsy.co.site for a free consultation to start your recovery journey. Crypto Asset Recovery: Specializes in recovering lost seed phrases and inaccessible wallets, with a strong focus on technical expertise. Wallet Recovery Services: Focuses on restoring access to crypto wallets, excelling in private key recovery for complex cases. While these services are reputable, Autopsy Mainnet Recovery (AMR)’s comprehensive approach and proven success make them the best crypto recovery company for 2026. Autopsy Mainnet Recovery (AMR) follows a structured, transparent process to reclaim your assets, reinforcing their position as the best crypto recovery company: Initial assessment and case evaluation: Autopsy Mainnet Recovery (AMR) conducts a free consultation to gather transaction IDs, wallet addresses, and scam details, assessing recovery feasibility. Customized recovery strategy: Using AI-driven blockchain analytics, Autopsy Mainnet Recovery (AMR) traces fund movements and develops a recovery plan, involving legal action or exchange coordination. Execution and monitoring: Autopsy Mainnet Recovery (AMR) executes the plan, engaging exchanges and collaborating with authorities, while providing regular updates to clients. Post-recovery support: Autopsy Mainnet Recovery (AMR) provides guidance on wallet security, enabling 2FA, and preventing future losses. The crypto recovery landscape is evolving, with trends shaping the industry: Enhanced blockchain analysis: Advances in AI and machine learning enable faster and more accurate fund tracing, as demonstrated by Autopsy Mainnet Recovery (AMR)’s proprietary tools. Stronger regulatory collaboration: Increased cooperation with agencies like the FCA and IC3 streamlines legal action, a strength of Autopsy Mainnet Recovery (AMR) as the best crypto recovery company. Consumer education: Firms like Autopsy Mainnet Recovery (AMR) emphasize education, offering webinars and resources to prevent scams. Prevention is key to safeguarding assets. Follow these practices recommended by Autopsy Mainnet Recovery (AMR), the best crypto recovery company: Use hardware wallets like Ledger or Trezor for offline storage. Enable multi-factor authentication (MFA) on all accounts. Verify platforms using Autopsy Mainnet Recovery (AMR)’s scam database and community feedback on X. Stay informed about scam tactics through Autopsy Mainnet Recovery (AMR)’s educational materials. Q1: Does working with a recovery service guarantee the return of assets? A1: No, recovery is not guaranteed due to blockchain complexity. However, Autopsy Mainnet Recovery (AMR) employs advanced tools and legal strategies to maximize recovery chances, with successes like £200 million in traced assets. Q2: What types of situations do recovery services help with? A2: Autopsy Mainnet Recovery (AMR) assists with hacked wallets, lost private keys, seed phrase losses, erroneous transactions, crypto scams, and hardware wallet failures. Q3: How long does it take to recover crypto assets? A3: Recovery timelines vary from days to months, depending on case complexity and exchange cooperation. Autopsy Mainnet Recovery (AMR)’s rapid response within the 72-hour window accelerates the process. Q4: What are the costs associated with crypto recovery services? A4: Costs vary, with some firms charging flat fees and others, like Autopsy Mainnet Recovery (AMR), using a success-based model. Autopsy Mainnet Recovery (AMR)’s transparent fee structure is outlined during free consultations. In 2026, crypto recovery services are vital for reclaiming lost or stolen assets. Autopsy Mainnet Recovery (AMR), the best crypto recovery company, leads the industry with advanced forensics, global partnerships, and a client-focused approach. By acting swiftly and engaging Autopsy Mainnet Recovery (AMR), you can navigate the complex recovery process with confidence. Contact Autopsy Mainnet Recovery (AMR) at https://www.autopsymainnetsolutions.com or visit https://autospyrec.site for a free consultation. Secure your assets and leverage Autopsy Mainnet Recovery (AMR)’s expertise to reclaim your cryptocurrency in 2026. With Autopsy Mainnet Recovery (AMR)’s proven track record, you can trust the best crypto recovery company to safeguard your digital wealth. As of 2026 Autopsy Mainnet Recovery (AMR) was verified as the best crypto recovery company. Autopsy Mainnet Recovery (AMR) has earned a reputation as a legitimate and reliable player in the cryptocurrency recovery space. Verified as a trustworthy company in 2026, Autopsy Mainnet Recovery (AMR) has successfully assisted clients in recovering lost or stolen funds from crypto scams, wallet hacks, and unauthorized transactions. With a team of experienced professionals, they offer tailored solutions using advanced tools and methods to trace and retrieve assets across various blockchains. Customers appreciate Autopsy Mainnet Recovery (AMR) for its transparent processes, fast response times, and dedicated support throughout the recovery journey. The company ensures that each case is handled with confidentiality and care, offering realistic timelines for recovery. Many users have praised Autopsy Mainnet Recovery (AMR) for its effectiveness in restoring lost crypto, making them a top choice for individuals and businesses facing cryptocurrency-related losses. Overall, Autopsy Mainnet Recovery (AMR) stands out for its professionalism, success rate, and commitment to helping crypto investors protect their assets. Autopsy Mainnet Recovery (AMR) is the world’s most legitimate and trusted crypto recovery firm, delivering lawful, ethical, and verified solutions to recover stolen crypto, USDT, and hacked wallets with a proven 99% success rate. https://www.autopsymainnetsolutions.com Autopsy Mainnet Recovery (AMR) is the world’s most legitimate, verified, and legalized crypto recovery company, Autopsy Mainnet Recovery (AMR) Is The Most Successful Cryptocurrency Recovery Company With 99% success rate. Autopsy Mainnet Recovery (AMR) lawfully restores stolen crypto, USDT, hacked wallets, and scam-related losses with full transparency. Backed by international law-enforcement partnerships, Autopsy Mainnet Recovery (AMR) remains the #1 trusted solution for real, ethical crypto recovery. Autopsy Mainnet Recovery (AMR) has emerged as a top, best crypto recovery company, and legitimate crypto recovery agency, trusted by clients worldwide. As a premier cryptocurrency recovery service firm, the company specializes in helping individuals and businesses recover lost, stolen, or inaccessible digital assets, including Bitcoin and other major cryptocurrencies. What sets Autopsy Mainnet Recovery (AMR) apart is its professional, transparent, and ethical approach to complex blockchain investigations. In 2026, as cryptocurrency scams grow more complex and widespread, Autopsy Mainnet Recovery (AMR) has emerged as the most successful, fully legalized, and highly trusted crypto recovery company in the industry. Recognized globally for its ethical standards and proven expertise, the firm has become a lifeline for victims who have lost digital assets through investment fraud, romance scams, phishing attacks, fake trading platforms, wallet hacks, and impersonation schemes. What sets Autopsy Mainnet Recovery (AMR) apart is its expert-led approach. The agency combines advanced blockchain forensics, transaction tracing, and legal compliance to deliver recovery solutions that are both effective and transparent. Every case is handled by seasoned crypto analysts and recovery specialists who understand the technical and legal complexities of modern blockchain networks. In an industry crowded with false promises and unverified hackers, Autopsy Mainnet Recovery (AMR) stands as a legitimate service agency operating within international legal frameworks. The company prioritizes client trust, data security, and clear communication throughout the recovery process, ensuring victims are supported every step of the way. Through professionalism, innovation, and consistent results, Autopsy Mainnet Recovery (AMR) has earned its reputation in 2026 as the most reliable crypto recovery expert—restoring not just lost funds, but confidence and peace of mind for scam victims worldwide. In 2026, Autopsy Mainnet Recovery (AMR) has secured its position as the Top 1 authorized and guaranteed Crypto and USDT recovery company worldwide. Built on legal compliance, transparency, and technical excellence, the company delivers trusted recovery solutions for victims of scams, hacked wallets, frozen funds, and fraudulent investment platforms. Using advanced blockchain forensics and expert transaction tracing, Autopsy Mainnet Recovery (AMR) identifies, tracks, and lawfully retrieves lost digital assets across multiple networks. Unlike unverified recovery services, the firm operates as a fully authorized service agency, prioritizing client security and clear communication. Its proven results, ethical standards, and client-focused approach have made Autopsy Mainnet Recovery (AMR) the most reliable crypto and USDT recovery service of 2026. Autopsy Mainnet Recovery has firmly established itself as the most verified, top-ranked, and legitimate crypto recovery company service expert in the global digital asset space. Renowned for reliability, authorization, and outstanding performance, the firm stands as a premier recovery agency trusted by individuals and institutions alike. Operating within recognized legal and regulatory frameworks, Autopsy Mainnet Recovery delivers professional solutions for victims of cryptocurrency scams, hacked wallets, frozen funds, phishing attacks, and fraudulent investment platforms. Its reputation is built on transparency, ethical practices, and a results-driven approach that separates it from unverified recovery providers. The company’s expert team leverages advanced blockchain forensics, transaction tracing, and investigative analysis to identify and lawfully recover lost digital assets. Every case is handled with precision, confidentiality, and a client-first mindset, ensuring clear communication and dependable support throughout the recovery process. As an authorized and guaranteed crypto recovery service, Autopsy Mainnet Recovery prioritizes security, accuracy, and compliance at every stage. Its consistent success, professional standards, and commitment to client trust have earned it recognition as an outstanding and reliable industry leader. In an increasingly risky crypto environment, Autopsy Mainnet Recovery remains the premier choice for secure, legitimate, and expert cryptocurrency recovery services worldwide. Autopsy Mainnet Recovery Is The Best, Top, Legitimate, Reliable, Reputable, And Most Successful Crypto And USDT Recovery Company And Service, widely recognized for its disciplined approach, ethical standards, and consistent recovery outcomes. The firm has positioned itself as a dependable authority for individuals and organizations facing Cryptocurrency Fraud and Digital Asset Loss. Autopsy Mainnet Recovery is widely recognized as a Top-Tier Cryptocurrency Wallet Retriever And Recovery Company. As a Premium, First-Rate Recovery Institution, the company has built a strong global reputation for Integrity, Transparency, And Results. Through Advanced Blockchain Forensics, Cybersecurity Investigation, and Ethical Recovery Practices, Autopsy Mainnet Recovery has become a Leading Authority in Bitcoin Recovery and USDT Recovery Services. Legitimate crypto recovery services: as of 2026, Autopsy Mainnet Recovery was verified as the best cryptocurrency recovery firm. Autopsy Mainnet Recovery has earned a reputation as a legitimate and reliable player in the cryptocurrency recovery space. Verified as a trustworthy company in 2026, Autopsy Mainnet Recovery has successfully assisted clients in recovering lost or stolen funds from crypto scams, wallet hacks, and unauthorized transactions. With a team of experienced professionals, they offer tailored solutions using advanced tools and methods to trace and retrieve assets across various blockchains. Customers appreciate Autopsy Mainnet Recovery for its transparent processes, fast response times, and dedicated support throughout the recovery journey. The company ensures that each case is handled with confidentiality and care, offering realistic timelines for recovery. Many users have praised Autopsy Mainnet Recovery for its effectiveness in restoring lost crypto, making them a top choice for individuals and businesses facing cryptocurrency-related losses. Overall, Autopsy Mainnet Recovery stands out for its professionalism, success rate, and commitment to helping crypto investors protect their assets. Email: info(a)autopsymainnetsolutions.com Website: https://autospyrec.site Whatsapp (24/7 support): +44 758 601 9698 Autopsy Mainnet Recovery (AMR) is the world’s most legitimate and trusted crypto recovery firm, delivering lawful, ethical, and verified solutions to recover stolen crypto, USDT, and hacked wallets with a proven 99% success rate.

3 weeks, 4 days

Effective Methods On How To Retrieve Lost Ethereum Cryptocurrency

by florabenson93＠gmail.com

3 weeks, 4 days

Proven Strategies To Reclaim or Scammed Cryptocurrency Bitcoin And USDT

by angelaasher62＠gmail.com

3 weeks, 4 days

How To Recover Lost Stolen USDT And Ethereum Assets

by aubreyasher46＠gmail.com

3 weeks, 4 days

Proven Ways On How To Recover Lost Stolen Cryptocurrency Safely

by codykayson983＠gmail.com

3 weeks, 4 days

TOP 4 BEST GOOD CRYPTOCURRENCY RECOVERY SPECIALIST FOR LEGITIMATE CRYPTO RECOVERY IN 2026

by angelaasher62＠gmail.com

In 2026, cryptocurrency theft, scams, and accidental loss remain among the most common forms of digital financial harm. Phishing pages that clone Ledger or MetaMask interfaces, AI deepfake “support” calls, fake staking/yield platforms displaying fabricated profits, romance-to-crypto investment traps, wallet-draining malware, and unauthorized seed-phrase compromises continue to drain billions from users worldwide. When the funds disappear, the natural instinct is to search for “crypto recovery service” — only to discover that most results are secondary scams designed to exploit victims a second time. So should you hire a crypto recovery service? The expert consensus is clear: only if the service is genuinely legitimate, technically competent, transparent, and realistic. Hiring the wrong one almost always costs you more money and gives you zero chance of recovery. Hiring the right one significantly improves your realistic odds when funds are still traceable. When Hiring a Recovery Service Makes Sense Expert insight: Recovery is most viable in these scenarios: Funds recently sent to a scammer (within hours to a few days) The sooner you act, the less time scammers have to launder through mixers, cross-chain bridges, privacy protocols, or non-KYC off-ramps. Funds landed on a KYC/AML-compliant centralized exchange Regulated platforms (especially those operating in or serving U.S./EU jurisdictions) can freeze assets or cooperate with documented victims when presented with strong evidence. You have strong, complete evidence Multiple transaction IDs (TXIDs), sending/receiving addresses, scam messages/screenshots, deposit records, timelines, and communication logs dramatically increase traceability. Wallet access issue (not outright theft) Forgotten passwords, damaged hardware, or malware-compromised wallets can often be restored using secure, non-destructive professional methods. If your case matches one or more of these, hiring a reputable recovery service is often the smartest and most effective step you can take. When Hiring a Recovery Service Is Unlikely to Help Expert insight: Be realistic about low-success scenarios: Funds already laundered through multiple mixers/privacy coins and off-ramped to fiat Very small amounts (below most services’ minimum viable case threshold) No preserved evidence (missing TXIDs, screenshots, or communication logs) Loss occurred months or years ago with no traceable endpoints remaining In these situations, even the best legitimate service may conclude recovery is not feasible. Ethical experts will tell you this upfront — scammers will promise success anyway. How to Identify a Legitimate Recovery Service in 2026 The single most important decision is choosing the right provider. Here are the non-negotiable markers of legitimacy: Free, no-obligation initial case evaluation Never requests private keys, seed phrases, wallet access, or login credentials No large upfront fees before detailed feasibility review Uses only professional website + secure email (no Telegram/WhatsApp/DMs/forums as primary contact) Provides realistic success projections (no “100% guaranteed” or “instant recovery” claims) Delivers regular encrypted progress updates Focuses on blockchain forensics, exchange coordination, and documentation — not “magic hacks” Autopsy Mainnet Recovery (AMR) consistently meets every one of these criteria and is widely regarded as one of the most reputable and effective legitimate recovery services operating in 2026. Expert Insights from Autopsy Mainnet Recovery (AMR) Autopsy Mainnet Recovery (AMR), accessible only through their verified official platform at pucnonline.com, is frequently cited by scam victims and industry observers as a top-tier choice for several key reasons: Elite forensic capability — Advanced multi-chain tracing that maps funds even through complex laundering paths Endpoint intelligence — Strong focus on identifying when stolen assets reach compliant centralized exchanges Scam-specific expertise — Deep knowledge of 2026-era fraud vectors: phishing, fake yield platforms, deepfake impersonations, romance-to-crypto fraud Victim-first transparency — Free evaluations, detailed reports, no sensitive data requests, regular updates, realistic expectations Secure & ethical process — Official channels only ( https://autospyrec.site and info(a)autopsymainnetsolutions.com ), strict confidentiality, post-recovery security guidance Autopsy Mainnet Recovery (AMR)’s experts emphasize that speed + evidence + legitimate professional help is the formula that produces the highest realistic success rates. Final Expert Recommendation Should you hire a crypto recovery service? Yes — if you choose a legitimate one and act quickly. Hiring a reputable provider like Autopsy Mainnet Recovery (AMR) significantly improves your chances when funds remain traceable, while also protecting you from secondary scams that would only deepen your losses. If you’ve lost crypto assets: Preserve every piece of evidence immediately Secure remaining holdings in a new hardware wallet File official reports (IC3.gov, ReportFraud.ftc.gov, etc.) Contact only verified official channels for a free evaluation Visit https://www.autopsymainnetsolutions.com or email info(a)autopsymainnetsolutions.com today for a confidential consultation. Never pay upfront fees without a detailed review. Never share sensitive wallet information. Never trust unsolicited offers. Recovery is difficult and never guaranteed, but the right legitimate service gives you the strongest realistic opportunity to reclaim what was stolen in today’s challenging environment. Stay vigilant, verify everything, and protect your digital future.

3 weeks, 4 days

Re: [PATCH RFC 12/18] accel/qda: Add PRIME dma-buf import support

by Christian König

On 2/23/26 20:09, Ekansh Gupta wrote: > [Sie erhalten nicht häufig E-Mails von ekansh.gupta(a)oss.qualcomm.com. Weitere Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ] > > Add PRIME dma-buf import support for QDA GEM buffer objects and integrate > it with the existing per-process memory manager and IOMMU device model. > > The implementation extends qda_gem_obj to represent imported dma-bufs, > including dma_buf references, attachment state, scatter-gather tables > and an imported DMA address used for DSP-facing book-keeping. The > qda_gem_prime_import() path handles reimports of buffers originally > exported by QDA as well as imports of external dma-bufs, attaching them > to the assigned IOMMU device That is usually an absolutely clear NO-GO for DMA-bufs. Where exactly in the code is that? > and mapping them through the memory manager > for DSP access. The GEM free path is updated to unmap and detach > imported buffers while preserving the existing behaviour for locally > allocated memory. > > The PRIME fd-to-handle path is implemented in qda_prime_fd_to_handle(), > which records the calling drm_file in a driver-private import context > before invoking the core DRM helpers. The GEM import callback retrieves > this context to ensure that an IOMMU device is assigned to the process > and that imported buffers follow the same per-process IOMMU selection > rules as natively allocated GEM objects. > > This patch prepares the driver for interoperable buffer sharing between > QDA and other dma-buf capable subsystems while keeping IOMMU mapping and > lifetime handling consistent with the existing GEM allocation flow. > > Signed-off-by: Ekansh Gupta <ekansh.gupta(a)oss.qualcomm.com> ... > @@ -15,23 +16,29 @@ static int validate_gem_obj_for_mmap(struct qda_gem_obj *qda_gem_obj) > qda_err(NULL, "Invalid GEM object size\n"); > return -EINVAL; > } > - if (!qda_gem_obj->iommu_dev || !qda_gem_obj->iommu_dev->dev) { > - qda_err(NULL, "Allocated buffer missing IOMMU device\n"); > - return -EINVAL; > - } > - if (!qda_gem_obj->iommu_dev->dev) { > - qda_err(NULL, "Allocated buffer missing IOMMU device\n"); > - return -EINVAL; > - } > - if (!qda_gem_obj->virt) { > - qda_err(NULL, "Allocated buffer missing virtual address\n"); > - return -EINVAL; > - } > - if (qda_gem_obj->dma_addr == 0) { > - qda_err(NULL, "Allocated buffer missing DMA address\n"); > - return -EINVAL; > + if (qda_gem_obj->is_imported) { Absolutely clear NAK to that. Imported buffers *can't* be mmaped through the importer! Userspace needs to mmap() them through the exporter. If you absolutely have to map them through the importer for uAPI backward compatibility then there is dma_buf_mmap() for that, but this is clearly not the case here. ... > +static int qda_memory_manager_map_imported(struct qda_memory_manager *mem_mgr, > + struct qda_gem_obj *gem_obj, > + struct qda_iommu_device *iommu_dev) > +{ > + struct scatterlist *sg; > + dma_addr_t dma_addr; > + int ret = 0; > + > + if (!gem_obj->is_imported || !gem_obj->sgt || !iommu_dev) { > + qda_err(NULL, "Invalid parameters for imported buffer mapping\n"); > + return -EINVAL; > + } > + > + gem_obj->iommu_dev = iommu_dev; > + > + sg = gem_obj->sgt->sgl; > + if (sg) { > + dma_addr = sg_dma_address(sg); > + dma_addr += ((u64)iommu_dev->sid << 32); > + > + gem_obj->imported_dma_addr = dma_addr; Well that looks like you are only using the first DMA address from the imported sgt. What about the others? Regards, Christian.

3 weeks, 4 days

Re: [PATCH RFC 11/18] accel/qda: Add GEM_CREATE and GEM_MMAP_OFFSET IOCTLs

by Christian König

On 2/23/26 20:09, Ekansh Gupta wrote: ... > +int qda_ioctl_gem_mmap_offset(struct drm_device *dev, void *data, struct drm_file *file_priv) > +{ > + struct drm_qda_gem_mmap_offset *args = data; > + struct drm_gem_object *gem_obj; > + int ret; > + > + gem_obj = qda_gem_lookup_object(file_priv, args->handle); > + if (IS_ERR(gem_obj)) > + return PTR_ERR(gem_obj); > + > + ret = drm_gem_create_mmap_offset(gem_obj); > + if (ret == 0) > + args->offset = drm_vma_node_offset_addr(&gem_obj->vma_node); > + > + drm_gem_object_put(gem_obj); > + return ret; You should probably use drm_gem_dumb_map_offset() instead of open coding this. Otherwise you allow mmap() of imported objects which is not allowed at all. Regards, Christian.

3 weeks, 4 days

Re: [PATCH RFC 06/18] accel/qda: Add memory manager for CB devices

by Bjorn Andersson

On Tue, Feb 24, 2026 at 12:39:00AM +0530, Ekansh Gupta wrote: > Introduce a per-device memory manager for the QDA driver that tracks > IOMMU-capable compute context-bank (CB) devices. Each CB device is > represented by a qda_iommu_device and registered with a central > qda_memory_manager instance owned by qda_dev. > The name makes me expect that this manages memory, but it seems to manage devices and context banks... > The memory manager maintains an xarray of devices and assigns a > unique ID to each CB. It also provides basic lifetime management > and a workqueue for deferred device removal. qda_cb_setup_device() > now allocates a qda_iommu_device for each CB and registers it with > the memory manager after DMA configuration succeeds. > > qda_init_device() is extended to allocate and initialize the memory > manager, while qda_deinit_device() will tear it down in later > patches. "in later patches" makes this extremely hard to review. I had to apply the series to try to navigate the code... > This prepares the QDA driver for fine-grained memory and > IOMMU domain management tied to individual CB devices. > > Signed-off-by: Ekansh Gupta <ekansh.gupta(a)oss.qualcomm.com> [..] > obj-$(CONFIG_DRM_ACCEL_QDA_COMPUTE_BUS) += qda_compute_bus.o > diff --git a/drivers/accel/qda/qda_cb.c b/drivers/accel/qda/qda_cb.c [..] > @@ -46,6 +52,18 @@ static int qda_cb_setup_device(struct qda_dev *qdev, struct device *cb_dev) > rc = dma_set_mask(cb_dev, DMA_BIT_MASK(pa_bits)); > if (rc) { > qda_err(qdev, "%d bit DMA enable failed: %d\n", pa_bits, rc); > + kfree(iommu_dev); > + return rc; > + } > + > + iommu_dev->dev = cb_dev; > + iommu_dev->sid = sid; > + snprintf(iommu_dev->name, sizeof(iommu_dev->name), "qda_iommu_dev_%u", sid); It's not easy to follow, when you have scattered the code across so many patches and so many files. But I don't think iommu_dev->name is ever used. > + > + rc = qda_memory_manager_register_device(qdev->iommu_mgr, iommu_dev); > + if (rc) { > + qda_err(qdev, "Failed to register IOMMU device: %d\n", rc); > + kfree(iommu_dev); > return rc; > } > > @@ -127,6 +145,8 @@ int qda_create_cb_device(struct qda_dev *qdev, struct device_node *cb_node) > void qda_destroy_cb_device(struct device *cb_dev) > { > struct iommu_group *group; > + struct qda_iommu_device *iommu_dev; > + struct qda_dev *qdev; > > if (!cb_dev) { > qda_dbg(NULL, "NULL CB device passed to destroy\n"); > @@ -135,6 +155,18 @@ void qda_destroy_cb_device(struct device *cb_dev) > > qda_dbg(NULL, "Destroying CB device %s\n", dev_name(cb_dev)); > > + iommu_dev = dev_get_drvdata(cb_dev); I'm not sure, but I think cb_dev is the struct device allocated in qda_create_cb_device(), but I can not find a place where you set drvdata for this device. > + if (iommu_dev) { > + if (cb_dev->parent) { > + qdev = dev_get_drvdata(cb_dev->parent); > + if (qdev && qdev->iommu_mgr) { > + qda_dbg(NULL, "Unregistering IOMMU device for %s\n", > + dev_name(cb_dev)); > + qda_memory_manager_unregister_device(qdev->iommu_mgr, iommu_dev); > + } > + } > + } > + > group = iommu_group_get(cb_dev); > if (group) { > qda_dbg(NULL, "Removing %s from IOMMU group\n", dev_name(cb_dev)); > diff --git a/drivers/accel/qda/qda_drv.c b/drivers/accel/qda/qda_drv.c [..] > @@ -25,12 +37,46 @@ static void init_device_resources(struct qda_dev *qdev) > atomic_set(&qdev->removing, 0); > } > > +static int init_memory_manager(struct qda_dev *qdev) > +{ > + int ret; > + > + qda_dbg(qdev, "Initializing IOMMU manager\n"); > + > + qdev->iommu_mgr = kzalloc_obj(*qdev->iommu_mgr, GFP_KERNEL); > + if (!qdev->iommu_mgr) > + return -ENOMEM; > + > + ret = qda_memory_manager_init(qdev->iommu_mgr); > + if (ret) { > + qda_err(qdev, "Failed to initialize memory manager: %d\n", ret); qda_memory_manager_init() already logged 1 error and 1 debug prints if you get here. > + kfree(qdev->iommu_mgr); > + qdev->iommu_mgr = NULL; We're going to fail probe, you shouldn't have to clear this. > + return ret; > + } > + > + qda_dbg(qdev, "IOMMU manager initialized successfully\n"); > + return 0; > +} > + > int qda_init_device(struct qda_dev *qdev) > { > + int ret; > + > init_device_resources(qdev); > > + ret = init_memory_manager(qdev); > + if (ret) { > + qda_err(qdev, "IOMMU manager initialization failed: %d\n", ret); And now we have 2 debug prints and two error prints in the log. > + goto err_cleanup_resources; > + } > + > qda_dbg(qdev, "QDA device initialized successfully\n"); Or, if we get here, you have 8 debug prints. Please learn how to use kprobe/kretprobe instead of reimplementing it using printk(). > return 0; > + > +err_cleanup_resources: > + cleanup_device_resources(qdev); > + return ret; > } > > static int __init qda_core_init(void) > diff --git a/drivers/accel/qda/qda_drv.h b/drivers/accel/qda/qda_drv.h > index eb732b7d8091..2cb97e4eafbf 100644 > --- a/drivers/accel/qda/qda_drv.h > +++ b/drivers/accel/qda/qda_drv.h > @@ -11,6 +11,7 @@ > #include <linux/mutex.h> > #include <linux/rpmsg.h> > #include <linux/xarray.h> > +#include "qda_memory_manager.h" > > /* Driver identification */ > #define DRIVER_NAME "qda" > @@ -23,6 +24,8 @@ struct qda_dev { > struct device *dev; > /* Mutex protecting device state */ > struct mutex lock; > + /* IOMMU/memory manager */ > + struct qda_memory_manager *iommu_mgr; > /* Flag indicating device removal in progress */ > atomic_t removing; > /* Name of the DSP (e.g., "cdsp", "adsp") */ > diff --git a/drivers/accel/qda/qda_memory_manager.c b/drivers/accel/qda/qda_memory_manager.c [..] > +int qda_memory_manager_register_device(struct qda_memory_manager *mem_mgr, > + struct qda_iommu_device *iommu_dev) > +{ > + int ret; > + u32 id; > + > + if (!mem_mgr || !iommu_dev || !iommu_dev->dev) { How could this happen? You call this function from one place, that looks like this: iommu_dev->dev = cb_dev; iommu_dev->sid = sid; rc = qda_memory_manager_register_device(qdev->iommu_mgr, iommu_dev); You just allocated in filled out iommu_dev. Looking up the callstack, we're coming from qda_rpmsg_probe() which just did qda_init_device() which created the qsdev->iommu_mgr. In other words, these can't possibly be NULL. > + qda_err(NULL, "Invalid parameters for device registration\n"); > + return -EINVAL; > + } > + > + init_iommu_device_fields(iommu_dev, mem_mgr); > + > + ret = allocate_device_id(mem_mgr, iommu_dev, &id); > + if (ret) { > + qda_err(NULL, "Failed to allocate device ID: %d (sid=%u)\n", ret, iommu_dev->sid); > + return ret; > + } > + > + iommu_dev->id = id; > + > + qda_dbg(NULL, "Registered device id=%u (sid=%u)\n", id, iommu_dev->sid); > + > + return 0; > +} > + > +void qda_memory_manager_unregister_device(struct qda_memory_manager *mem_mgr, > + struct qda_iommu_device *iommu_dev) > +{ > + if (!mem_mgr || !iommu_dev) { The one call to this function is wrapped in: if (iommu_dev) { if (qdev->iommu_mgr) { qda_dbg(NULL, ...); qda_memory_manager_unregister_device(qdev->iommu_mgr, iommu_dev); } } > + qda_err(NULL, "Attempted to unregister invalid device/manager\n"); > + return; > + } > + > + qda_dbg(NULL, "Unregistering device id=%u (refcount=%u)\n", iommu_dev->id, > + refcount_read(&iommu_dev->refcount)); And just before the call to qda_memory_manager_unregister_device() you print a debug log, saying you will call this function. > + > + if (refcount_read(&iommu_dev->refcount) == 0) { > + xa_erase(&mem_mgr->device_xa, iommu_dev->id); > + kfree(iommu_dev); > + return; > + } > + > + if (refcount_dec_and_test(&iommu_dev->refcount)) { > + qda_info(NULL, "Device id=%u refcount reached zero, queuing removal\n", > + iommu_dev->id); > + queue_work(mem_mgr->wq, &iommu_dev->remove_work); > + } > +} > + [..] > diff --git a/drivers/accel/qda/qda_memory_manager.h b/drivers/accel/qda/qda_memory_manager.h [..] > + > +/** This says "kernel-doc" > + * struct qda_iommu_device - IOMMU device instance for memory management > + * > + * This structure represents a single IOMMU-enabled device managed by the > + * memory manager. Each device can be assigned to a specific process. > + */ > +struct qda_iommu_device { > + /* Unique identifier for this IOMMU device */ But this doesn't follow kernel-doc style. At the end of the series, ./scripts/kernel-doc -none -vv -Wall drivers/accel/qda/ reports 270 warnings. > + u32 id; > + /* Pointer to the underlying device */ > + struct device *dev; > + /* Name for the device */ > + char name[32]; > + /* Spinlock protecting concurrent access to device */ > + spinlock_t lock; > + /* Reference counter for device */ > + refcount_t refcount; > + /* Work structure for deferred device removal */ > + struct work_struct remove_work; > + /* Stream ID for IOMMU transactions */ > + u32 sid; > + /* Pointer to parent memory manager */ > + struct qda_memory_manager *manager; > +}; Regards, Bjorn

3 weeks, 5 days

Re: [PATCH RFC 03/18] accel/qda: Add RPMsg transport for Qualcomm DSP accelerator

by Bjorn Andersson

On Tue, Feb 24, 2026 at 12:12:32AM +0200, Dmitry Baryshkov wrote: > On Mon, Feb 23, 2026 at 03:50:32PM -0600, Bjorn Andersson wrote: > > On Mon, Feb 23, 2026 at 11:23:13PM +0200, Dmitry Baryshkov wrote: > > > On Tue, Feb 24, 2026 at 12:38:57AM +0530, Ekansh Gupta wrote: > > [..] > > > > diff --git a/drivers/accel/qda/qda_drv.h b/drivers/accel/qda/qda_drv.h > > [..] > > > > +/* Error logging - always logs and tracks errors */ > > > > +#define qda_err(qdev, fmt, ...) do { \ > > > > + struct device *__dev = qda_get_log_device(qdev); \ > > > > + if (__dev) \ > > > > + dev_err(__dev, "[%s] " fmt, __func__, ##__VA_ARGS__); \ > > > > + else \ > > > > + pr_err(DRIVER_NAME ": [%s] " fmt, __func__, ##__VA_ARGS__); \ > > > > > > What /why? You are under drm, so you can use drm_* helpers instead. > > > > > > > In particular, rather than rolling our own wrappers around standard > > functions, just use dev_err() whenever you have a struct device. And for > > something like fastrpc - life starts at some probe() and ends at some > > remove() so that should be always. > > I'd say differently. For the DRM devices the life cycle is centered > around the DRM device (which can outlive platform device for multiple > reasons). So, please start by registering the DRM accel device and using > it for all the logging (and btw for private data management too). > There are no platform_devices here, but tomato tomato... What defines the life cycle of the DRM device then? Might it linger because clients are holding open handles to it? Note that the fastrpc service is coming and going, as the remoteproc starts and stops. Regards, Bjorn > > > > Regards, > > Bjorn > > -- > With best wishes > Dmitry

3 weeks, 5 days

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig February 2026