From: Greg KH <gregkh@linuxfoundation.org>
To: Xinhu Wu <xinhu.wu@unisoc.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, orsonzhai@gmail.com,
baolin.wang@linux.alibaba.com, zhang.lyra@gmail.com,
heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
xinhuwu.unisoc@gmail.com, zhiyong.liu@unisoc.com,
peak.yang@unisoc.com, teng.zhang1@unisoc.com,
bruce.chen@unisoc.com, surong.pang@unisoc.com,
xingxing.luo@unisoc.com
Subject: Re: [PATCH V2 1/2] usb: typec: Support sprd_pmic_typec driver
Date: Mon, 11 Dec 2023 08:53:24 +0100 [thread overview]
Message-ID: <2023121122-jelly-password-6eac@gregkh> (raw)
In-Reply-To: <20231211074120.27958-2-xinhu.wu@unisoc.com>
On Mon, Dec 11, 2023 at 03:41:19PM +0800, Xinhu Wu wrote:
> +config TYPEC_SPRD_PMIC
> + tristate "SPRD Serials PMICs Typec Controller"
> + help
> + Say Y or M here if your system has a SPRD PMIC Type-C port controller.
> +
> + If you choose to build this driver as a dynamically linked module, the
> + module will be called sprd_pmic_typec.ko.
> + SPRD_PMIC_TYPEC notify usb, phy, charger, and analog audio to proceed
> + with work
I do not understand these last two lines, are you sure they are correct?
> +
> +
Nit, only one blank line is needed here.
> +static irqreturn_t sprd_pmic_typec_interrupt(int irq, void *data)
> +{
> + struct sprd_pmic_typec *sc = data;
> + u32 event;
> + int ret;
> +
> + dev_info(sc->dev, "%s enter line %d\n", __func__, __LINE__);
debugging information? Please remove.
> + ret = regmap_read(sc->regmap, sc->base + SC27XX_INT_MASK, &event);
> + if (ret)
> + return ret;
> +
> + event &= sc->var_data->event_mask;
> +
> + ret = regmap_read(sc->regmap, sc->base + SC27XX_STATUS, &sc->state);
> + if (ret)
> + goto clear_ints;
> +
> + sc->state &= sc->var_data->state_mask;
> +
> + if (event & SC27XX_ATTACH_INT) {
> + ret = sprd_pmic_typec_connect(sc, sc->state);
> + if (ret)
> + dev_warn(sc->dev, "failed to register partner\n");
> + } else if (event & SC27XX_DETACH_INT) {
> + sprd_pmic_typec_disconnect(sc, sc->state);
> + }
> +
> +clear_ints:
> + regmap_write(sc->regmap, sc->base + sc->var_data->int_clr, event);
> +
> + dev_info(sc->dev, "now works as DRP and is in %d state, event %d\n",
> + sc->state, event);
When drivers work properly, they are quiet, please never spam the kernel
log for normal operations.
> +static ssize_t
> +sprd_pmic_typec_cc_polarity_role_show(struct device *dev, struct device_attribute *attr,
> + char *buf)
> +{
> + struct sprd_pmic_typec *sc = dev_get_drvdata(dev);
> +
> + return snprintf(buf, 5, "%s\n", sprd_pmic_typec_cc_polarity_roles[sc->cc_polarity]);
sysfs_emit() please.
> +}
> +static DEVICE_ATTR_RO(sprd_pmic_typec_cc_polarity_role);
Where is this new sysfs file documented?
> + ret = sysfs_create_groups(&sc->dev->kobj, sprd_pmic_typec_groups);
You just raced with userspace and lost, and better yet:
> + if (ret < 0)
> + dev_err(sc->dev, "failed to create cc_polarity %d\n", ret);
You do not even clean up properly here.
Please use the default groups for the driver and it should work just
fine.
> + ret = sprd_pmic_typec_set_rtrim(sc);
> + if (ret < 0) {
> + dev_err(sc->dev, "failed to set typec rtrim %d\n", ret);
> + goto error;
> + }
> +
> + ret = devm_request_threaded_irq(sc->dev, sc->irq, NULL,
> + sprd_pmic_typec_interrupt,
> + IRQF_EARLY_RESUME | IRQF_ONESHOT,
> + dev_name(sc->dev), sc);
Are you sure you can use devm_() here?
> +static int sprd_pmic_typec_remove(struct platform_device *pdev)
> +{
> + struct sprd_pmic_typec *sc = platform_get_drvdata(pdev);
> +
> + sysfs_remove_groups(&sc->dev->kobj, sprd_pmic_typec_groups);
Again, should not be needed if you use the default groups of the
platform driver.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-11 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 7:41 [PATCH V2 0/2] usb: typec: sprd: Add Unisoc PMIC typec driver Xinhu Wu
2023-12-11 7:41 ` [PATCH V2 1/2] usb: typec: Support sprd_pmic_typec driver Xinhu Wu
2023-12-11 7:53 ` Greg KH [this message]
2023-12-11 17:35 ` Rob Herring
2023-12-11 18:51 ` kernel test robot
2023-12-11 19:11 ` kernel test robot
2023-12-11 7:41 ` [PATCH V2 2/2] dt-bindings: usb: Add an Spreadtrum pmic typec yaml Xinhu Wu
2023-12-11 8:20 ` Rob Herring
2023-12-11 19:35 ` kernel test robot
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=2023121122-jelly-password-6eac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bruce.chen@unisoc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=peak.yang@unisoc.com \
--cc=robh+dt@kernel.org \
--cc=surong.pang@unisoc.com \
--cc=teng.zhang1@unisoc.com \
--cc=xingxing.luo@unisoc.com \
--cc=xinhu.wu@unisoc.com \
--cc=xinhuwu.unisoc@gmail.com \
--cc=zhang.lyra@gmail.com \
--cc=zhiyong.liu@unisoc.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).