From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@iki.fi>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v8 2/2] On Semi AR0521 sensor driver
Date: Tue, 01 Mar 2022 13:34:28 +0100 [thread overview]
Message-ID: <m38rtt7sx7.fsf@t19.piap.pl> (raw)
In-Reply-To: <20220301093107.ihokyp4xptkzpbpc@uno.localdomain> (Jacopo Mondi's message of "Tue, 1 Mar 2022 10:31:07 +0100")
Jacopo Mondi <jacopo@jmondi.org> writes:
> In subject
>
> "media: i2c:"
>
> Same for 1/2 where permutation of "media: dt-bindings: i2c:" are used
> when adding bindings for media i2c drivers.
You know, it's rather hard to know all these tiny requirements. Let
alone get them right all the time.
>> + pm_runtime_set_active(&client->dev);
>> + pm_runtime_enable(&client->dev);
>> + pm_runtime_idle(&client->dev);
>
> Do you have an _idle() callback ? This seems a no-op to me, or am I
> mistaken ? (runtime_pm is still cryptic to me sometimes)
Do you mean only the pm_runtime_idle()? Sakari just requested I add it.
> Can't you just remove power_on() if it's not needed ?
It wouldn't work without CONFIG_PM then, would it?
> There still are a few checkpatch warnings which might be worth
> considering but nothing huge.
Do you mean this?
WARNING: Block comments use * on subsequent lines
#411: FILE: drivers/media/i2c/ar0521.c:351:
+ /* Reset gain, the sensor may produce all white pixels without
+ this */
WARNING: Block comments use a trailing */ on a separate line
#411: FILE: drivers/media/i2c/ar0521.c:351:
+ this */
... which are about a single comment which I had to wrap to fit in 80
columns, hardly a block comment by my standards. Not to mention Linus
saying...
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2022-03-01 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:33 [PATCH v8 0/2] On Semi AR0521 sensor driver Krzysztof Hałasa
2022-03-01 8:38 ` [PATCH v8 1/2] " Krzysztof Hałasa
2022-03-01 8:41 ` [PATCH v8 2/2] " Krzysztof Hałasa
2022-03-01 9:31 ` Jacopo Mondi
2022-03-01 12:34 ` Krzysztof Hałasa [this message]
2022-03-01 14:30 ` Jacopo Mondi
2022-03-02 6:39 ` Krzysztof Hałasa
2022-04-12 11:41 ` Krzysztof Hałasa
2022-05-06 6:10 ` Krzysztof Hałasa
2022-06-29 23:37 ` Sakari Ailus
2022-06-30 4:29 ` Krzysztof Hałasa
2022-06-30 7:13 ` Sakari Ailus
2022-06-20 11:47 ` Krzysztof Hałasa
2022-03-01 13:39 ` 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=m38rtt7sx7.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=devicetree@vger.kernel.org \
--cc=jacopo@jmondi.org \
--cc=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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