2018-05-06 21:58:06 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ */
|
2014-02-26 22:59:18 +00:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2013 Google, Inc
|
|
|
|
|
*
|
|
|
|
|
* (C) Copyright 2012
|
|
|
|
|
* Pavel Herrmann <morpheus.ibis@gmail.com>
|
|
|
|
|
* Marek Vasut <marex@denx.de>
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _DM_PLATDATA_H
|
|
|
|
|
#define _DM_PLATDATA_H
|
|
|
|
|
|
2014-10-07 05:49:13 +00:00
|
|
|
#include <linker_lists.h>
|
|
|
|
|
|
2014-07-23 12:55:17 +00:00
|
|
|
/**
|
|
|
|
|
* struct driver_info - Information required to instantiate a device
|
|
|
|
|
*
|
2015-07-06 18:54:22 +00:00
|
|
|
* NOTE: Avoid using this except in extreme circumstances, where device tree
|
|
|
|
|
* is not feasible (e.g. serial driver in SPL where <8KB of SRAM is
|
|
|
|
|
* available). U-Boot's driver model uses device tree for configuration.
|
|
|
|
|
*
|
2014-09-28 13:52:24 +00:00
|
|
|
* @name: Driver name
|
2014-07-23 12:55:17 +00:00
|
|
|
* @platdata: Driver-specific platform data
|
dm: core: Expand platdata for of-platdata devices
Devices which use of-platdata have their own platdata. However, in many
cases the driver will have its own auto-alloced platdata, for use with the
device tree. The ofdata_to_platdata() method converts the device tree
settings to platdata.
With of-platdata we would not normally allocate the platdata since it is
provided by the U_BOOT_DEVICE() declaration. However this is inconvenient
since the of-platdata struct is closely tied to the device tree properties.
It is unlikely to exactly match the platdata needed by the driver.
In fact a useful approach is to declare platdata in the driver like this:
struct r3288_mmc_platdata {
struct dtd_rockchip_rk3288_dw_mshc of_platdata;
/* the 'normal' fields go here */
};
In this case we have dt_platadata available, but the normal fields are not
present, since ofdata_to_platdata() is never called. In fact driver model
doesn't allocate any space for the 'normal' fields, since it sees that there
is already platform data attached to the device.
To make this easier, adjust driver model to allocate the full size of the
struct (i.e. platdata_auto_alloc_size from the driver) and copy in the
of-platdata. This means that when the driver's bind() method is called,
the of-platdata will be present, followed by zero bytes for the empty
'normal field' portion.
A new DM_FLAG_OF_PLATDATA flag is available that indicates that the platdata
came from of-platdata. When the allocation/copy happens, the
DM_FLAG_ALLOC_PDATA flag will be set as well. The dtoc tool is updated to
output the platdata_size field, since U-Boot has no other way of knowing
the size of the of-platdata struct.
Signed-off-by: Simon Glass <sjg@chromium.org>
2016-07-04 17:58:18 +00:00
|
|
|
* @platdata_size: Size of platform data structure
|
2020-06-25 04:10:11 +00:00
|
|
|
* @dev: Device created from this structure data
|
2014-07-23 12:55:17 +00:00
|
|
|
*/
|
2014-02-26 22:59:18 +00:00
|
|
|
struct driver_info {
|
2014-07-23 12:55:17 +00:00
|
|
|
const char *name;
|
|
|
|
|
const void *platdata;
|
dm: core: Expand platdata for of-platdata devices
Devices which use of-platdata have their own platdata. However, in many
cases the driver will have its own auto-alloced platdata, for use with the
device tree. The ofdata_to_platdata() method converts the device tree
settings to platdata.
With of-platdata we would not normally allocate the platdata since it is
provided by the U_BOOT_DEVICE() declaration. However this is inconvenient
since the of-platdata struct is closely tied to the device tree properties.
It is unlikely to exactly match the platdata needed by the driver.
In fact a useful approach is to declare platdata in the driver like this:
struct r3288_mmc_platdata {
struct dtd_rockchip_rk3288_dw_mshc of_platdata;
/* the 'normal' fields go here */
};
In this case we have dt_platadata available, but the normal fields are not
present, since ofdata_to_platdata() is never called. In fact driver model
doesn't allocate any space for the 'normal' fields, since it sees that there
is already platform data attached to the device.
To make this easier, adjust driver model to allocate the full size of the
struct (i.e. platdata_auto_alloc_size from the driver) and copy in the
of-platdata. This means that when the driver's bind() method is called,
the of-platdata will be present, followed by zero bytes for the empty
'normal field' portion.
A new DM_FLAG_OF_PLATDATA flag is available that indicates that the platdata
came from of-platdata. When the allocation/copy happens, the
DM_FLAG_ALLOC_PDATA flag will be set as well. The dtoc tool is updated to
output the platdata_size field, since U-Boot has no other way of knowing
the size of the of-platdata struct.
Signed-off-by: Simon Glass <sjg@chromium.org>
2016-07-04 17:58:18 +00:00
|
|
|
#if CONFIG_IS_ENABLED(OF_PLATDATA)
|
|
|
|
|
uint platdata_size;
|
2020-06-25 04:10:11 +00:00
|
|
|
struct udevice *dev;
|
dm: core: Expand platdata for of-platdata devices
Devices which use of-platdata have their own platdata. However, in many
cases the driver will have its own auto-alloced platdata, for use with the
device tree. The ofdata_to_platdata() method converts the device tree
settings to platdata.
With of-platdata we would not normally allocate the platdata since it is
provided by the U_BOOT_DEVICE() declaration. However this is inconvenient
since the of-platdata struct is closely tied to the device tree properties.
It is unlikely to exactly match the platdata needed by the driver.
In fact a useful approach is to declare platdata in the driver like this:
struct r3288_mmc_platdata {
struct dtd_rockchip_rk3288_dw_mshc of_platdata;
/* the 'normal' fields go here */
};
In this case we have dt_platadata available, but the normal fields are not
present, since ofdata_to_platdata() is never called. In fact driver model
doesn't allocate any space for the 'normal' fields, since it sees that there
is already platform data attached to the device.
To make this easier, adjust driver model to allocate the full size of the
struct (i.e. platdata_auto_alloc_size from the driver) and copy in the
of-platdata. This means that when the driver's bind() method is called,
the of-platdata will be present, followed by zero bytes for the empty
'normal field' portion.
A new DM_FLAG_OF_PLATDATA flag is available that indicates that the platdata
came from of-platdata. When the allocation/copy happens, the
DM_FLAG_ALLOC_PDATA flag will be set as well. The dtoc tool is updated to
output the platdata_size field, since U-Boot has no other way of knowing
the size of the of-platdata struct.
Signed-off-by: Simon Glass <sjg@chromium.org>
2016-07-04 17:58:18 +00:00
|
|
|
#endif
|
2014-02-26 22:59:18 +00:00
|
|
|
};
|
|
|
|
|
|
2015-07-06 18:54:22 +00:00
|
|
|
/**
|
|
|
|
|
* NOTE: Avoid using these except in extreme circumstances, where device tree
|
|
|
|
|
* is not feasible (e.g. serial driver in SPL where <8KB of SRAM is
|
|
|
|
|
* available). U-Boot's driver model uses device tree for configuration.
|
|
|
|
|
*/
|
2014-02-26 22:59:18 +00:00
|
|
|
#define U_BOOT_DEVICE(__name) \
|
|
|
|
|
ll_entry_declare(struct driver_info, __name, driver_info)
|
|
|
|
|
|
2014-10-02 01:57:21 +00:00
|
|
|
/* Declare a list of devices. The argument is a driver_info[] array */
|
|
|
|
|
#define U_BOOT_DEVICES(__name) \
|
|
|
|
|
ll_entry_declare_list(struct driver_info, __name, driver_info)
|
|
|
|
|
|
2020-06-25 04:10:11 +00:00
|
|
|
/* Get a pointer to a given driver */
|
|
|
|
|
#define DM_GET_DEVICE(__name) \
|
|
|
|
|
ll_entry_get(struct driver_info, __name, driver_info)
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* dm_populate_phandle_data() - Populates phandle data in platda
|
|
|
|
|
*
|
|
|
|
|
* This populates phandle data with an U_BOOT_DEVICE entry get by
|
|
|
|
|
* DM_GET_DEVICE. The implementation of this function will be done
|
|
|
|
|
* by dtoc when parsing dtb.
|
|
|
|
|
*/
|
|
|
|
|
void dm_populate_phandle_data(void);
|
2014-02-26 22:59:18 +00:00
|
|
|
#endif
|
