linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mweseloh42@gmail.com (Marcus Weseloh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] spi: dts: sun4i: Add support for hardware-based wait time between words
Date: Mon, 14 Dec 2015 09:08:09 +0100	[thread overview]
Message-ID: <CAGNoLaMR48FP6LA6OCUiwBFpja_inx47f-7hzLC3+=6td6oeaQ@mail.gmail.com> (raw)
In-Reply-To: <CAGNoLaOckrgv5NP6eTOt8shj5f069DKFrxx+8afydqcAZH5HMw@mail.gmail.com>

2015-12-14 8:31 GMT+01:00 Marcus Weseloh <mweseloh42@gmail.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

      reply	other threads:[~2015-12-14  8:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 22:45 [PATCH v2] spi: dts: sun4i: Add support for inter-word wait cycles using the SPI Wait Clock Register Marcus Weseloh
2015-12-12  9:19 ` [linux-sunxi] " Priit Laes
2015-12-12 10:44   ` Marcus Weseloh
2015-12-13 21:07 ` Maxime Ripard
2015-12-13 21:52   ` Marcus Weseloh
2015-12-13 23:04 ` [PATCH v3] spi: dts: sun4i: Add support for hardware-based wait time between words Marcus Weseloh
2015-12-13 23:08   ` Mark Brown
2015-12-13 23:23     ` Marcus Weseloh
2015-12-14 10:57       ` Mark Brown
2015-12-14  1:29   ` Rob Herring
2015-12-14  7:31     ` Marcus Weseloh
2015-12-14  8:08       ` Marcus Weseloh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGNoLaMR48FP6LA6OCUiwBFpja_inx47f-7hzLC3+=6td6oeaQ@mail.gmail.com' \
    --to=mweseloh42@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).