From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Andy Shevchenko <andy@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH 6/6] media: atomisp: Switch to int3472 driver sensor GPIO mapping code
Date: Thu, 8 May 2025 17:09:26 +0300 (EEST) [thread overview]
Message-ID: <d0ed8b99-1663-5fef-baf4-d094b618a919@linux.intel.com> (raw)
In-Reply-To: <1a5cca5a-4bb1-4ac5-aefc-b1ef0e693914@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
On Thu, 8 May 2025, Hans de Goede wrote:
> Hi,
>
> On 8-May-25 3:56 PM, Hans de Goede wrote:
> > Hi,
> >
> > On 8-May-25 3:48 PM, Ilpo Järvinen wrote:
> >> On Thu, 8 May 2025, Hans de Goede wrote:
> >>> On 8-May-25 10:34 AM, Andy Shevchenko wrote:
> >>>> On Wed, May 7, 2025 at 9:48 PM Hans de Goede <hdegoede@redhat.com> wrote:
> >>>>>
> >>>>> Replace the duplicate code for calling the special Intel camera sensor GPIO
> >>>>> type _DSM (79234640-9e10-4fea-a5c1-b5aa8b19756f) and mapping GPIOs to
> >>>>> the sensor with a call to int3472_discrete_parse_crs() from the int3472
> >>>>> driver.
> >>>>>
> >>>>> Besides avoiding code duplication the int3472 version of the code also
> >>>>> supports more features, like mapping the powerdown GPIO to a regulator on
> >>>>> the mt9m114 which is necessary to make the camera on the Asus T100TA work.
> >>>>
> >>>> ...
> >>>>
> >>>> Don't you need the Kconfig(s) update to have proper dependencies all
> >>>> over these cases?
> >>>
> >>> Yes I do, I thought about doing this already but forgot to actually
> >>> do it, thank you for catching this.
> >>>
> >>> When I've some time for it I'll prepare a v2 of just this patch
> >>> addressing this and your s/then/than/ remark.
> >>>
> >>> Since you and Sakari are happy with them patches 1-5 can be picked up
> >>> and merged by Ilpo as is, so I do not plan to send a v2 of those.
> >>
> >> Thanks for the quick reviews.
> >>
> >> I took patch 1-5 into the review-ilpo-next branch with one typo in
> >> change log fixed (reser -> reset).
> >
> > Great, thank you!
>
> Ilpo, I just noticed that Sakari typod his Reviewed-by, it reads:
>
> Reviwed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>
> and this is also how the tag looks in review-ilpo-next now.
> so missing an 'e' you probably will want to fix this.
>
> Also Sakari gave an Acked-by for patch 6/6, but since he did so
> in a reply to the cover letter all 5 (1-5) patches now have:
>
> Reviwed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>
> so besides adding the missing 'e' you probably will also want
> to drop the entire Acked-by.
Yeah, a perfect example of tunnel vision. I was looking specifically
whether those reviewed-bys got added by b4 into all patches but failed to
notice any of those errors despite staring at the very lines. Thanks for
letting me know, I'll fix them.
--
i.
next prev parent reply other threads:[~2025-05-08 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 18:47 [PATCH 0/6] platform/x86: int3472: Allow re-using sensor GPIO mapping in atomisp Hans de Goede
2025-05-07 18:47 ` [PATCH 1/6] platform/x86: int3472: Move common.h to public includes, symbols to INTEL_INT3472 Hans de Goede
2025-05-07 18:47 ` [PATCH 2/6] platform/x86: int3472: Stop using devm_gpiod_get() Hans de Goede
2025-05-07 18:47 ` [PATCH 3/6] platform/x86: int3472: Export int3472_discrete_parse_crs() Hans de Goede
2025-05-07 18:47 ` [PATCH 4/6] platform/x86: int3472: Remove unused sensor_config struct member Hans de Goede
2025-05-07 18:47 ` [PATCH 5/6] platform/x86: int3472: For mt9m114 sensors map powerdown to powerenable Hans de Goede
2025-05-07 18:47 ` [PATCH 6/6] media: atomisp: Switch to int3472 driver sensor GPIO mapping code Hans de Goede
2025-05-08 8:34 ` Andy Shevchenko
2025-05-08 13:18 ` Hans de Goede
2025-05-08 13:48 ` Ilpo Järvinen
2025-05-08 13:56 ` Hans de Goede
2025-05-08 14:06 ` Hans de Goede
2025-05-08 14:09 ` Ilpo Järvinen [this message]
2025-07-04 9:37 ` Hans de Goede
2025-05-08 8:36 ` [PATCH 0/6] platform/x86: int3472: Allow re-using sensor GPIO mapping in atomisp Andy Shevchenko
2025-05-08 8:37 ` Andy Shevchenko
2025-05-08 13:15 ` Hans de Goede
2025-05-08 14:00 ` Hans de Goede
2025-05-08 14:51 ` Andy Shevchenko
2025-05-08 10:22 ` Sakari Ailus
2025-05-08 14:55 ` Andy Shevchenko
2025-05-08 15:38 ` 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=d0ed8b99-1663-5fef-baf4-d094b618a919@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=platform-driver-x86@vger.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