From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: James Ogletree <James.Ogletree@cirrus.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Fred Treven <Fred.Treven@cirrus.com>,
Ben Bright <Ben.Bright@cirrus.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Jeff LaBundy <jeff@labundy.com>, Joel Stanley <joel@jms.id.au>,
Arnd Bergmann <arnd@arndb.de>, Jacky Bai <ping.bai@nxp.com>,
Jean Delvare <jdelvare@suse.de>,
Eddie James <eajames@linux.ibm.com>,
Markus Schneider-Pargmann <msp@baylibre.com>,
ChiYuan Huang <cy_huang@richtek.com>,
Randy Dunlap <rdunlap@infradead.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"patches@cirrus.com" <patches@cirrus.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] Input: cs40l50 - Initial support for Cirrus Logic CS40L50
Date: Tue, 15 Aug 2023 21:23:59 +0200 [thread overview]
Message-ID: <afefa654-4f9a-121e-7d1b-76d9dcd778f7@linaro.org> (raw)
In-Reply-To: <D4B53566-9F7D-46DA-8BAE-0572B9A8AA7A@cirrus.com>
On 15/08/2023 17:56, James Ogletree wrote:
>
>
>> On Aug 10, 2023, at 1:17 AM, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 09/08/2023 21:10, James Ogletree wrote:
>>
>>> +
>>> +static int cs40l50_cs_dsp_init(struct cs40l50_private *cs40l50)
>>> +{
>>> + cs40l50->dsp.num = 1;
>>> + cs40l50->dsp.type = WMFW_HALO;
>>> + cs40l50->dsp.dev = cs40l50->dev;
>>> + cs40l50->dsp.regmap = cs40l50->regmap;
>>> + cs40l50->dsp.base = CS40L50_DSP1_CORE_BASE;
>>> + cs40l50->dsp.base_sysinfo = CS40L50_DSP1_SYS_INFO_ID;
>>> + cs40l50->dsp.mem = cs40l50_dsp_regions;
>>> + cs40l50->dsp.num_mems = ARRAY_SIZE(cs40l50_dsp_regions);
>>> + cs40l50->dsp.lock_regions = 0xFFFFFFFF;
>>> + cs40l50->dsp.no_core_startstop = true;
>>> + cs40l50->dsp.client_ops = &cs40l50_cs_dsp_client_ops;
>>> +
>>> + return cs_dsp_halo_init(&cs40l50->dsp);
>>> +}
>>> +
>>> +int cs40l50_probe(struct cs40l50_private *cs40l50)
>>> +{
>>> + int error, i, irq;
>>> + u32 val;
>>> +
>>> + mutex_init(&cs40l50->lock);
>>> +
>>> + error = devm_regulator_bulk_get(cs40l50->dev, ARRAY_SIZE(cs40l50_supplies),
>>> + cs40l50_supplies);
>>> + if (error)
>>> + return dev_err_probe(cs40l50->dev, error, "Failed to request supplies\n");
>>> +
>>> + error = regulator_bulk_enable(ARRAY_SIZE(cs40l50_supplies), cs40l50_supplies);
>>> + if (error)
>>> + return dev_err_probe(cs40l50->dev, error, "Failed to enable supplies\n");
>>> +
>>> + cs40l50->reset_gpio = devm_gpiod_get_optional(cs40l50->dev, "reset", GPIOD_OUT_HIGH);
>>
>> None of the lines above or below seem to be wrapped according to Linux
>> coding style (80).
>
> This patch abides by the 100-column line length limit which checkpatch.pl enforces.
Checkpatch does not enforce 100, because it accepts also 80. It
complains if something is longer than 100, but coding style is still the
same. Format everything according to coding style and use 100 only if it
increases readability.
> However, I can see how some of the lines might be less jarring to the eyes if wrapped.
> That will be addressed in V4.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-15 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 19:10 [PATCH v3 0/2] Add support for CS40L50 James Ogletree
2023-08-09 19:10 ` [PATCH v3 1/2] dt-bindings: input: cirrus,cs40l50: Support " James Ogletree
2023-08-10 6:19 ` Krzysztof Kozlowski
2023-08-09 19:10 ` [PATCH v3 2/2] Input: cs40l50 - Initial support for Cirrus Logic CS40L50 James Ogletree
2023-08-10 6:17 ` Krzysztof Kozlowski
2023-08-15 15:56 ` James Ogletree
2023-08-15 19:23 ` Krzysztof Kozlowski [this message]
2023-08-10 10:30 ` Charles Keepax
2023-08-15 22:33 ` James Ogletree
2023-08-16 8:11 ` Charles Keepax
2023-08-11 4:07 ` Jeff LaBundy
2023-08-16 21:02 ` James Ogletree
2023-08-22 12:43 ` Jeff LaBundy
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=afefa654-4f9a-121e-7d1b-76d9dcd778f7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Ben.Bright@cirrus.com \
--cc=Fred.Treven@cirrus.com \
--cc=James.Ogletree@cirrus.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=jdelvare@suse.de \
--cc=jeff@labundy.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=patches@cirrus.com \
--cc=ping.bai@nxp.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).