linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,  Shawn Guo <shawnguo@kernel.org>,
	 Sascha Hauer <s.hauer@pengutronix.de>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	 Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-arm-kernel@lists.infradead.org,
	 linux-media@vger.kernel.org
Subject: Re: [PATCH] media: i2c: ar0521: fix spellos
Date: Mon, 22 Jan 2024 06:28:41 +0100	[thread overview]
Message-ID: <m3y1ci543a.fsf@t19.piap.pl> (raw)
In-Reply-To: <20240111043302.15641-1-rdunlap@infradead.org> (Randy Dunlap's message of "Wed, 10 Jan 2024 20:33:01 -0800")

Hi Randy,

Good catches, thanks for your work.

Randy Dunlap <rdunlap@infradead.org> writes:

> Fix spelling mistakes as reported by codespell.

Acked-by: Krzysztof Hałasa <khalasa@piap.pl>

> --- a/drivers/media/i2c/ar0521.c
> +++ b/drivers/media/i2c/ar0521.c
> @@ -314,7 +314,7 @@ static void ar0521_calc_pll(struct ar052
>          * In the clock tree:
>          * MIPI_CLK = PIXEL_CLOCK * bpp / 2 / 2
>          *
> -        * Generic pixel_rate to bus clock frequencey equation:
> +        * Generic pixel_rate to bus clock frequency equation:
>          * MIPI_CLK = V4L2_CID_PIXEL_RATE * bpp / lanes / 2
>          *
>          * From which we derive the PIXEL_CLOCK to use in the clock tree:
> @@ -327,7 +327,7 @@ static void ar0521_calc_pll(struct ar052
>          *
>          * TODO: in case we have less data lanes we have to reduce the desired
>          * VCO not to exceed the limits specified by the datasheet and
> -        * consequentially reduce the obtained pixel clock.
> +        * consequently reduce the obtained pixel clock.
>          */
>         pixel_clock = AR0521_PIXEL_CLOCK_RATE * 2 / sensor->lane_count;
>         bpp = ar0521_code_to_bpp(sensor);
> @@ -806,7 +806,7 @@ static const struct initial_reg {
>         REGS(be(0x3F00),
>              be(0x0017),  /* 3F00: BM_T0 */
>              be(0x02DD),  /* 3F02: BM_T1 */
> -            /* 3F04: if Ana_gain less than 2, use noise_floor0, multipl */
> +            /* 3F04: if Ana_gain less than 2, use noise_floor0, multiply */
>              be(0x0020),
>              /* 3F06: if Ana_gain between 4 and 7, use noise_floor2 and */
>              be(0x0040),
>
>

-- 
Krzysztof "Chris" Hałasa

Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2024-01-22  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  4:33 [PATCH] media: i2c: ar0521: fix spellos Randy Dunlap
2024-01-22  5:28 ` Krzysztof Hałasa [this message]

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=m3y1ci543a.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnguo@kernel.org \
    /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).