From: Kate Hsuan <hpa@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev
Cc: Kate Hsuan <hpa@redhat.com>
Subject: [PATCH 0/3] Remove #ifdef ISP2401 and unifying sh_css_sp_group structure
Date: Mon, 5 Jun 2023 18:29:00 +0800 [thread overview]
Message-ID: <20230605102903.924283-1-hpa@redhat.com> (raw)
sh_css_sp_group structure was managed by #ifdef ISP2401. The configuration
structure was also determined in compile time which means we have to
compile the kernel code twice for each ISP2400 and ISP2401.
In order to determine the ISP types in runtime, the configuration
structure needs to be unified. It allows can be used to configure both
types of ISP. Since the length of the sh_css_sp_group for ISP2400 and
ISP2401 is different, before submitting the configuration to ISP, the data
has to be carefully put the necessary part to a buffer and then submitted
to the ISP.
Kate Hsuan (3):
media: atomisp: sh_css_internal: Unifying sh_css_sp_group to remove
#ifdef ISP2401
atomisp: sh_css_params: write the sp_group config according to the ISP
model
media: atomisp: ia_css_debug: remove unused codes
.../runtime/debug/interface/ia_css_debug.h | 6 --
.../pci/runtime/debug/src/ia_css_debug.c | 76 +------------------
.../media/atomisp/pci/sh_css_internal.h | 35 +++------
.../staging/media/atomisp/pci/sh_css_params.c | 37 ++++++++-
4 files changed, 48 insertions(+), 106 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-05 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:29 Kate Hsuan [this message]
2023-06-05 10:29 ` [PATCH 1/3] media: atomisp: sh_css_internal: Unifying sh_css_sp_group to remove #ifdef ISP2401 Kate Hsuan
2023-06-06 11:03 ` Hans de Goede
2023-06-05 10:29 ` [PATCH 2/3] atomisp: sh_css_params: write the sp_group config according to the ISP model Kate Hsuan
2023-06-05 11:10 ` Dan Carpenter
2023-06-06 2:34 ` Kate Hsuan
2023-06-06 11:02 ` Hans de Goede
2023-06-06 13:19 ` Hans de Goede
2023-06-07 3:20 ` Kate Hsuan
2023-06-05 10:29 ` [PATCH 3/3] media: atomisp: ia_css_debug: remove unused codes Kate Hsuan
2023-06-06 10:50 ` Hans de Goede
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=20230605102903.924283-1-hpa@redhat.com \
--to=hpa@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).