linux-kernel - setting up of platform device archdata?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <8AD41167-5FB1-4C42-83A7-9F0CC6AF69AA@kernel.crashing.org>
Date:	Tue, 3 Aug 2010 08:43:30 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Greg KH <greg@...ah.com>
Cc:	"linuxppc-dev@...abs.org list" <linuxppc-dev@...abs.org>,
	"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: setting up of platform device archdata?

Greg,

We are running into in issue in that we need the platform device archdata setup before platform_device_add gets called since we need some data in archdata setup to allow the bus notifiers to work properly.  On PPC we need this to get the dma masks setup properly that we than use in the bus notifiers to determine if we need SWIOTLB support for a given device or not.  Any suggestions on how to do this? Something like below?

struct platform_device *platform_device_alloc(const char *name, int id)

...
        if (pa) {
                strcpy(pa->name, name);
                pa->pdev.name = pa->name;
                pa->pdev.id = id;
                device_initialize(&pa->pdev.dev);
                pa->pdev.dev.release = platform_device_release;
#ifdef ARCH_HAS_PDEV_ARCHDATA_SETUP
		arch_setup_pdev_archdata(&pa->pdev.dev);
#endif
        }

- k--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/