From: "Leonardo Brás" <leobras.c@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 1/3] staging: fbtft: Includes description to mutex and spinlock - Style
Date: Thu, 9 Aug 2018 19:33:56 -0300 [thread overview]
Message-ID: <63297a43a9683cb6d925da67242c9e2c92fa9316.1533853354.git.leobras.c@gmail.com> (raw)
In-Reply-To: <cover.1533853354.git.leobras.c@gmail.com>
Adds comments explaining what are the spinlock and mutex used for.
Signed-off-by: Leonardo Brás <leobras.c@gmail.com>
---
drivers/staging/fbtft/fbtft.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h
index 798a8fe98e95..958835da433c 100644
--- a/drivers/staging/fbtft/fbtft.h
+++ b/drivers/staging/fbtft/fbtft.h
@@ -203,7 +203,7 @@ struct fbtft_par {
u8 *buf;
u8 startbyte;
struct fbtft_ops fbtftops;
- spinlock_t dirty_lock;
+ spinlock_t dirty_lock; /* Protects dirty_lines_{start,end} */
unsigned int dirty_lines_start;
unsigned int dirty_lines_end;
struct {
@@ -219,7 +219,7 @@ struct fbtft_par {
} gpio;
const s16 *init_sequence;
struct {
- struct mutex lock;
+ struct mutex lock; /* Mutex for Gamma curve locking */
u32 *curves;
int num_values;
int num_curves;
--
2.18.0
next prev parent reply other threads:[~2018-08-09 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 22:33 [PATCH v3 0/3] Style changes Leonardo Brás
2018-08-09 22:33 ` Leonardo Brás [this message]
2018-08-09 22:34 ` [PATCH v3 2/3] staging: fbtft: Replaces (1 << n) for macro BIT(n) - Style Leonardo Brás
2018-08-09 22:34 ` [PATCH v3 3/3] staging: fbtft: Corrects long index line " Leonardo Brás
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=63297a43a9683cb6d925da67242c9e2c92fa9316.1533853354.git.leobras.c@gmail.com \
--to=leobras.c@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/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).