From: Lame Morupisi <lamemorupisi12@gmail.com>
To: hansg@kernel.org
Cc: mchehab@kernel.org, sakari.ailus@linux.intel.com,
andy@kernel.org, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Lame Morupisi <lamemorupisi12@gmail.com>
Subject: [PATCH v2] staging: media: atomisp: Clarify MIPI frame layout comment
Date: Mon, 9 Nov 2026 06:12:23 +0000 [thread overview]
Message-ID: <20261109061223.17144-1-lamemorupisi12@gmail.com> (raw)
In-Reply-To: <20261108122840.85622-1-lamemorupisi12@gmail.com>
Clarify the description of the MIPI frame memory layout by
explaining the meaning of optional fields and payload words.
Leave the frame layout diagram unchanged to preserve its
existing representation.
Signed-off-by: Lame Morupisi <lamemorupisi12@gmail.com>
---
drivers/staging/media/atomisp/pci/sh_css_mipi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/pci/sh_css_mipi.c b/drivers/staging/media/atomisp/pci/sh_css_mipi.c
index 971b685cd..09c2b1286 100644
--- a/drivers/staging/media/atomisp/pci/sh_css_mipi.c
+++ b/drivers/staging/media/atomisp/pci/sh_css_mipi.c
@@ -130,7 +130,8 @@ ia_css_mipi_frame_calculate_size(const unsigned int width,
even_line_bytes = odd_line_bytes;
}
- /* a frame represented in memory: ()- optional; data - payload words.
+ /* Frame representation in memory: () denotes optional fields;
+ * data denotes payload words.
* addr 0 1 2 3 4 5 6 7:
* first SOF (SOL) PACK_H data data data data data
* data data data data data data data data
--
2.56.0
next prev parent reply other threads:[~2026-11-09 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 12:28 [PATCH] staging: media: atomisp: Fix block comment formatting Lame Morupisi
2026-11-09 6:12 ` Lame Morupisi [this message]
2026-11-09 6:45 ` [PATCH v2] staging: media: atomisp: Clarify MIPI frame layout comment Dan Carpenter
2026-11-09 7:16 ` Andy Shevchenko
2026-11-09 7:02 ` [PATCH] staging: media: atomisp: Fix block comment formatting Andy Shevchenko
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=20261109061223.17144-1-lamemorupisi12@gmail.com \
--to=lamemorupisi12@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®