linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] media: hi556: Fixes for x86 support
Date: Thu, 26 Jun 2025 13:42:30 +0200	[thread overview]
Message-ID: <75b2787e-1a07-4878-b101-8bc8cd9f0363@kernel.org> (raw)
In-Reply-To: <20250531190534.94684-1-hansg@kernel.org>

Hi Sakari,

On 31-May-25 21:05, Hans de Goede wrote:
> Hi All,
> 
> Here are 2 hi556 fixes which together fix hi556 camera sensors not working
> on various x86 laptop models. This has been tested and confirmed to fix
> the camera not working on a Dell Latitude 7450:
> https://bugzilla.redhat.com/show_bug.cgi?id=2368506
> 
> It would be nice if these can be queued up as fixes for 6.16-rc#.

What is the status if this series, you had one review-remark
on patch 2/2 which I've answered, so from my pov this is still
ready and it would be good to get this upstream since it fixes
the cameras on some HP laptops.

Regards,
 
Hans








> Hans de Goede (2):
>   media: hi556: Fix reset GPIO timings
>   media: hi556: Support full range of power rails
> 
>  drivers/media/i2c/hi556.c | 47 +++++++++++++++++++++++----------------
>  1 file changed, 28 insertions(+), 19 deletions(-)
> 
> 
> base-commit: 5e1ff2314797bf53636468a97719a8222deca9ae


  parent reply	other threads:[~2025-06-26 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31 19:05 [PATCH 0/2] media: hi556: Fixes for x86 support Hans de Goede
2025-05-31 19:05 ` [PATCH 1/2] media: hi556: Fix reset GPIO timings Hans de Goede
2025-05-31 19:05 ` [PATCH 2/2] media: hi556: Support full range of power rails Hans de Goede
2025-06-06  7:17   ` Sakari Ailus
2025-06-07 16:05     ` Hans de Goede
2025-06-26 11:42 ` Hans de Goede [this message]
2025-06-26 11:49   ` [PATCH 0/2] media: hi556: Fixes for x86 support Sakari Ailus

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=75b2787e-1a07-4878-b101-8bc8cd9f0363@kernel.org \
    --to=hansg@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --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).