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


Groups > linux.kernel > #1602414

Re: [PATCH 2/2] serdev: Add minimal bus locking API

From Andrey Smirnov <andrew.smirnov@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 2/2] serdev: Add minimal bus locking API
Date 2017-03-16 15:50 +0100
Message-ID <tlET2-88W-79@gated-at.bofh.it> (permalink)
References <tkUZQ-Q3-21@gated-at.bofh.it> <tkUZQ-Q3-33@gated-at.bofh.it> <tl438-7nX-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Mar 14, 2017 at 4:20 PM, Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Tue, Mar 14, 2017 at 3:48 PM, Andrey Smirnov
> <andrew.smirnov@gmail.com> wrote:
>> Add minimal bus locking API which is useful for serial devices that
>> implement request-reply protocol
>
> Can you put an example here?
>
> I'm not sure mutex is needed at all.

My use case is a "supervisory" microcontroller connected to SoC via
UART various aspects of which are exposed via MFD. I saw this kind of
"device design pattern" a number of times in my career, so I thought
and abstraction to help dealing with cases like that might be useful.

However, since Rob mentioned that API's expectation is that any such
locking is driver's responsibility, I'll drop this patch.

Thanks,
Andrey Smirnov

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


Thread

[PATCH 2/2] serdev: Add minimal bus locking API Andrey Smirnov <andrew.smirnov@gmail.com> - 2017-03-14 14:50 +0100
  Re: [PATCH 2/2] serdev: Add minimal bus locking API Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-03-15 00:30 +0100
    Re: [PATCH 2/2] serdev: Add minimal bus locking API Andrey Smirnov <andrew.smirnov@gmail.com> - 2017-03-16 15:50 +0100
  Re: [PATCH 2/2] serdev: Add minimal bus locking API Rob Herring <robh@kernel.org> - 2017-03-15 15:30 +0100

csiph-web