| /rk3399_rockchip-uboot/test/dm/ |
| H A D | spi.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/drivers/spi/ |
| H A D | soft_spi.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| H A D | spi-uclass.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/drivers/misc/ |
| H A D | cros_ec_spi.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/drivers/mtd/spi/ |
| H A D | sandbox.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| H A D | sf_probe.c | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/include/ |
| H A D | spi.h | d0cff03e187cc1de3d6b477b92c376aae27c95e8 Sun Jan 25 15:27:12 UTC 2015 Simon Glass <sjg@chromium.org> dm: spi: Move slave details to child platdata
At present we go through various contortions to store the SPI slave's chip
select in its private data. This only exists when the slave is active so
must be set up when it is probed. Until the device is probed we don't
actually know what chip select it will appear on.
However, now that we can support per-child platform data, we can use that
instead. This allows us to set up the chip select when the child is bound,
and avoid the messy contortions.
Unfortunately this is a fairly large change and it seems to be difficult to
break it down further.
Signed-off-by: Simon Glass <sjg@chromium.org>
|