Re: [PATCH V9 0/2] Add support for aw96103/aw96105 proximity sensor

[Jonathan Cameron <Jonathan.Cameron@Huawei.com>]

On Tue, 3 Sep 2024 06:03:04 +0000
<wangshuaijie@awinic.com> wrote:

> On Sat, 31 Aug 2024 15:07:24 +0100, jic23@kernel.org wrote:
> >On Tue, 27 Aug 2024 08:02:27 +0000
> >wangshuaijie@awinic.com wrote:
> >\r  
> >> From: shuaijie wang <wangshuaijie@awinic.com>
> >> 
> >> Add drivers that support Awinic aw96103/aw96105 proximity sensors.
> >> 
> >> The aw9610x series are high-sensitivity capacitive proximity detection
> >> sensors. This device detects human proximity and assists electronic devices
> >> in reducing specific absorption rate (SAR) to pass SAR related certifications.
> >> The device reduces RF power and reduces harm when detecting human proximity. 
> >> Increase power and improve signal quality when the human body is far away.
> >> 
> >> The specific absorption rate (SAR) is a metric that measures the degree of
> >> absorption of electromagnetic radiation emitted by wireless devices,
> >> such as mobile phones and tablets, by human tissue.
> >> 
> >> This patch implements device initialization, registration,
> >> I/O operation handling and interrupt handling, and passed basic testing.\r  
> >I made one trivial tweak to add static to the iio_info declaration and
> >applied to the togreg branch of iio.git, initially pushed out as testing
> >for 0-day to see if it can find any issues we missed.
> >
> >Thanks,
> >
> >Jonathan\r  
> 
> Hi Jonathan,
> 
> Thank you very much for your help and suggestions, which have been very
> beneficial to me. May I ask if I need to continue modifying my patch?
> If not, please inform me of the approximate time for review and merging.

It's already merged.
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=a369e1d1a10790f63b4b858dc74b53730146754f

That will be tested by the autobuilders + I need to rebase the whole
tree on char-misc once Greg (hopefully) takes a pull request that is outstanding.

That isn't relevant for your patch, but there is some other work queued
up that has dependencies on fixes that went upstream quicker.

This 'should' make the coming merge window so should be in v6.12 in
about 3 months time.  You can develop additional features on top of it
now but they are unlikely to make the 6.12 cycle as there is only about
a week left.

Jonathan

> 
> I look forward to your reply so that I can better plan my subsequent work.
> 
> Kind regards,
> Wang Shuaijie