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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 03 Apr 2014 17:05:33 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Pallala, Ramakrishna" <ramakrishna.pallala@...el.com>
Cc:	"mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
	"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Linaro-acpi] How to pass I2C platform_data under ACPI

On Thursday 03 April 2014 13:59:18 Pallala, Ramakrishna wrote:
> >> We definitely don't want per-board match entries, that does not scale.
> >> The driver should be reasonably generic and get all the necessary data 
> >> out of well-defined tables. You can have different IDs when there are 
> >> only a few cases that are actually relevant, but it has to be 
> >> conceivable that the same driver get used on future hardware without 
> >> changes.
> >
> >Yes, I meant that when the platform data information is not available
> >in ACPI namespace, then (and only then) pass the data by means of different IDs.
> >
> >Preferably this information is included in the ACPI namespace.
> 
> The idea is use the single platform_data struct  and initiaze it 
> accordingly from the driver's __init call based on the board/platform.

In general, you should think of it as being isolated from the board or
platform question, and not rely on an an initcall to do this for you.
A device driver, in particular for a device on something like an i2c
bus, should be able to figure out all the dependencies in its own
probe() function, without code on the platform side or in a specific
driver initcall.

What information it needs of course depends on the specific device,
but if you boot using FDT or ACPI, all the information you need should
be encoded in the data passed from the boot loader in a generic and
documented fashion. What data specifically do you want to pass here
that was previously encoded in platform data?

	Arnd
--
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/

Powered by blists - more mailing lists