On Mon, Apr 28, 2014 at 10:23:26PM +0200, Marek Vasut wrote:
On Monday, April 28, 2014 at 05:53:39 AM, Huang Shijie wrote:
We need the SPI NOR child node to store some specific features, such as the
dummy cycles for the DDR Quad read.
But now, we only have the @dev field in the
On Tuesday, April 29, 2014 at 07:18:34 AM, Huang Shijie wrote:
On Mon, Apr 28, 2014 at 10:23:26PM +0200, Marek Vasut wrote:
On Monday, April 28, 2014 at 05:53:39 AM, Huang Shijie wrote:
We need the SPI NOR child node to store some specific features, such as
the dummy cycles for the DDR
On Tue, Apr 29, 2014 at 08:54:24AM +0200, Marek Vasut wrote:
On Tuesday, April 29, 2014 at 07:18:34 AM, Huang Shijie wrote:
For the m25p80.c, @dev stands for a child node for the SPI master,
and it points to a spi_device{}. Yes, in this case, the dev-of_node is
NULL.
But for the
On Monday, April 28, 2014 at 05:53:39 AM, Huang Shijie wrote:
We need the SPI NOR child node to store some specific features, such as the
dummy cycles for the DDR Quad read.
But now, we only have the @dev field in the spi_nor{}. The @dev may points
to a spi_device{} for m25p80, while it may
We need the SPI NOR child node to store some specific features, such as the
dummy cycles for the DDR Quad read.
But now, we only have the @dev field in the spi_nor{}. The @dev may points to a
spi_device{} for m25p80, while it may points to a platform_deivice{} for the
SPI NOR controller, such as
