[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGNoLaMR48FP6LA6OCUiwBFpja_inx47f-7hzLC3+=6td6oeaQ@mail.gmail.com>
Date: Mon, 14 Dec 2015 09:08:09 +0100
From: Marcus Weseloh <mweseloh42@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: linux-sunxi <linux-sunxi@...glegroups.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Mark Brown <broonie@...nel.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>,
devicetree <devicetree@...r.kernel.org>,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
"Mailing List, Arm" <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3] spi: dts: sun4i: Add support for hardware-based wait
time between words
2015-12-14 8:31 GMT+01:00 Marcus Weseloh <mweseloh42@...il.com>:
> [...]
>>> + /* Setup wait time between words */
>>> + of_property_read_u32(spi->dev.of_node, "spi-word-wait-ns",
>>> + &wait_ns);
>>
>> Read this in probe and save the value rather than fetching every
>> transfer.
>
> But this is a slave property I'm using here. If I read and store it in
> probe in the spi-sun4i driver, I won't have access to the slave node
> property, will I?
Sorry, I think I get it now. I would need to read the value in SPI
core, when the slave device gets probed. I will send an updated patch.
Thanks,
Marcus
--
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