Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1630283

Re: [PATCH RFC 0/5] *** SPI Slave mode support ***

From Geert Uytterhoeven <geert@linux-m68k.org>
Newsgroups linux.kernel
Subject Re: [PATCH RFC 0/5] *** SPI Slave mode support ***
Date 2017-04-25 10:20 +0200
Message-ID <tA3Rx-28G-29@gated-at.bofh.it> (permalink)
References (3 earlier) <tw27E-5Bu-11@gated-at.bofh.it> <tzJSO-5YI-27@gated-at.bofh.it> <tzLBh-72B-35@gated-at.bofh.it> <tzM4h-7tv-15@gated-at.bofh.it> <tA3y9-1M8-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Jiada,

On Tue, Apr 25, 2017 at 9:56 AM, Jiada Wang <jiada_wang@mentor.com> wrote:
> On 04/24/2017 06:10 AM, Geert Uytterhoeven wrote:
>> On Mon, Apr 24, 2017 at 2:48 PM, Jiada Wang<jiada_wang@mentor.com>  wrote:
>>> On 04/24/2017 03:55 AM, Geert Uytterhoeven wrote:
>>>> On Fri, Apr 14, 2017 at 7:39 AM, Jiada Wang<jiada_wang@mentor.com>
>>>> wrote:
>>>>> Our use case is to use spidev as an interface to communicate with
>>>>> external
>>>>> SPI master devices.
>>>>> meanwhile the SPI bus controller can also act as master device to send
>>>>> data
>>>>> to other
>>>>> SPI slave devices on the board.
>>>>
>>>> That sounds a bit hackish to me. SPI was never meant to be a
>>>> multi-master
>>>> bus.
>>>> While it can be done, you will need external synchronization (signals)
>>>> to
>>>> avoid conflicts between the SPI masters.
>>>
>>> It doesn't need to be a multi-master bus,
>>> for example A is master device for slave device B.
>>> while B has its own slave device C
>>> for each SPI connection A<=>  B, and B<=>  C, there is only one master
>>> device.
>>>
>>> and I think from use case point of view, it's very normal,
>>> one CPU upon receives command from external SPI master device,
>>> it writes data to its own slave device (EEPROM) connected to it.
>>
>> So "A<=>  B" and "B<=>  C" are two distinct SPI buses?
>> Or do they share some signals?
>>
>> Your comment seems to suggest otherwise:
>
> the use case of
> "A (master) <=> B (slave)", "B (master) <=> C(slave)", do share MISO and
> MOSI lines,
> but there is no SS line between A and C. so for each SPI slave device, there
> is only one
> master device.

Do you share CLK, too? Then you need a slave select from B to C.
If you use a separate clock, the slave select from B to C can be optional.

> so I think the question becomes whether the above mentioned hardware setup
> is valid or not.

It's a non-conventional SPI bus setup, but it can work, provided you have
some form of synchronization between A and B.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH RFC 0/5] *** SPI Slave mode support *** <jiada_wang@mentor.com> - 2017-04-13 14:20 +0200
  [PATCH RFC 2/5] spi: spidev: use different name for SPI controller slave mode device <jiada_wang@mentor.com> - 2017-04-13 14:20 +0200
  Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Mark Brown <broonie@kernel.org> - 2017-04-13 15:00 +0200
    Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Geert Uytterhoeven <geert@linux-m68k.org> - 2017-04-13 21:50 +0200
      Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Jiada Wang <jiada_wang@mentor.com> - 2017-04-14 07:40 +0200
        Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Geert Uytterhoeven <geert@linux-m68k.org> - 2017-04-24 13:00 +0200
          Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Jiada Wang <jiada_wang@mentor.com> - 2017-04-24 14:50 +0200
            Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Geert Uytterhoeven <geert@linux-m68k.org> - 2017-04-24 15:20 +0200
              Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Jiada Wang <jiada_wang@mentor.com> - 2017-04-25 10:00 +0200
                Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Uwe Kleine-König          <u.kleine-koenig@pengutronix.de> - 2017-04-25 10:20 +0200
                Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Geert Uytterhoeven <geert@linux-m68k.org> - 2017-04-25 10:20 +0200
          Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Mark Brown <broonie@kernel.org> - 2017-04-25 12:40 +0200
            Re: [PATCH RFC 0/5] *** SPI Slave mode support *** Jiada Wang <jiada_wang@mentor.com> - 2017-04-27 08:50 +0200

csiph-web