From: Pin-yen Lin <treapking@chromium.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <robert.foss@linaro.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Daniel Scally" <djrscally@gmail.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Prashant Malani" <pmalani@chromium.org>,
"Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Xin Ji" <xji@analogixsemi.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Hsin-Yi Wang" <hsinyi@chromium.org>,
linux-kernel@vger.kernel.org,
"Allen Chen" <allen.chen@ite.com.tw>,
linux-acpi@vger.kernel.org, "Lyude Paul" <lyude@redhat.com>,
dri-devel@lists.freedesktop.org, chrome-platform@lists.linux.dev,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Marek Vasut" <marex@denx.de>,
devicetree@vger.kernel.org, "Stephen Boyd" <swboyd@chromium.org>,
"Douglas Anderson" <dianders@chromium.org>,
"Imre Deak" <imre.deak@intel.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Kees Cook" <keescook@chromium.org>,
"Khaled Almahallawy" <khaled.almahallawy@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"shaomin Deng" <dengshaomin@cdjrlc.com>
Subject: Re: [PATCH v7 3/9] drm/display: Add Type-C switch helpers
Date: Sat, 7 Jan 2023 17:16:35 +0800 [thread overview]
Message-ID: <CAEXTbpdg9C5pFVXo7fKSc_vWAczv_OthjbRA7DZVnENuNfwQfA@mail.gmail.com> (raw)
In-Reply-To: <Y7bvnOLcuJvvp/v1@smile.fi.intel.com>
Hi Andy,
Thanks for the review.
On Thu, Jan 5, 2023 at 11:41 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Thu, Jan 05, 2023 at 09:24:51PM +0800, Pin-yen Lin wrote:
> > Add helpers to register and unregister Type-C "switches" for bridges
> > capable of switching their output between two downstream devices.
> >
> > The helper registers USB Type-C mode switches when the "mode-switch"
> > and the "data-lanes" properties are available in Device Tree.
>
> ...
>
> > + port_data->typec_mux = typec_mux_register(dev, &mux_desc);
> > + if (IS_ERR(port_data->typec_mux)) {
> > + ret = PTR_ERR(port_data->typec_mux);
> > + dev_err(dev, "Mode switch register for port %d failed: %d\n",
> > + port_num, ret);
> > + }
> > +
> > + return ret;
>
> ...
>
> > + struct device_node *sw;
>
> > + int ret = 0;
>
> It's easy to break things if you squeeze more code in the future in this
> function, so I recommend to split assignment to be closer to its first user
> (see below).
>
> > + for_each_child_of_node(port, sw) {
> > + if (of_property_read_bool(sw, "mode-switch"))
> > + switch_desc->num_typec_switches++;
> > + }
> > +
> > + if (!switch_desc->num_typec_switches) {
> > + dev_warn(dev, "No Type-C switches node found\n");
>
> > + return ret;
>
> return 0;
Thanks for the suggestion. I'll update this in v8.
>
> > + }
> > +
> > + switch_desc->typec_ports = devm_kcalloc(
> > + dev, switch_desc->num_typec_switches,
> > + sizeof(struct drm_dp_typec_port_data), GFP_KERNEL);
> > +
> > + if (!switch_desc->typec_ports)
> > + return -ENOMEM;
>
> > + /* Register switches for each connector. */
> > + for_each_child_of_node(port, sw) {
> > + if (!of_property_read_bool(sw, "mode-switch"))
> > + continue;
> > + ret = drm_dp_register_mode_switch(dev, sw, switch_desc, data, mux_set);
> > + if (ret) {
> > + dev_err(dev, "Failed to register mode switch: %d\n", ret);
> > + of_node_put(sw);
> > + break;
> > + }
> > + }
>
> > + if (ret)
> > + drm_dp_unregister_typec_switches(switch_desc);
> > +
> > + return ret;
>
> Why not adding a goto label?
I didn't know that goto label is preferred even when there are no
duplicated code blocks in the function.
I'll update this accordingly in v8.
>
> ret = drm_dp_register_mode_switch(dev, sw, switch_desc, data, mux_set);
> if (ret)
> goto err_unregister_typec_switches;
>
> return 0;
>
> err_unregister_typec_switches:
> of_node_put(sw);
> drm_dp_unregister_typec_switches(switch_desc);
> dev_err(dev, "Failed to register mode switch: %d\n", ret);
> return ret;
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Best regards,
Pin-yen
next prev parent reply other threads:[~2023-01-07 9:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 13:24 [PATCH v7 0/9] Register Type-C mode-switch in DP bridge endpoints Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 1/9] device property: Add remote endpoint to devcon matcher Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 2/9] platform/chrome: cros_ec_typec: Purge blocking switch devlinks Pin-yen Lin
2023-01-05 15:32 ` Andy Shevchenko
2023-01-07 8:57 ` Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 3/9] drm/display: Add Type-C switch helpers Pin-yen Lin
2023-01-05 15:41 ` Andy Shevchenko
2023-01-07 9:16 ` Pin-yen Lin [this message]
2023-01-06 1:23 ` kernel test robot
2023-01-05 13:24 ` [PATCH v7 4/9] dt-bindings: drm/bridge: anx7625: Add mode-switch support Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 5/9] drm/bridge: anx7625: Check for Type-C during panel registration Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 6/9] drm/bridge: anx7625: Register Type C mode switches Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 7/9] dt/bindings: drm/bridge: it6505: Add mode-switch support Pin-yen Lin
2023-01-06 12:48 ` Krzysztof Kozlowski
2023-01-07 9:19 ` Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 8/9] drm/bridge: it6505: Fix Kconfig indentation Pin-yen Lin
2023-01-05 13:24 ` [PATCH v7 9/9] drm/bridge: it6505: Register Type C mode switches Pin-yen Lin
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=CAEXTbpdg9C5pFVXo7fKSc_vWAczv_OthjbRA7DZVnENuNfwQfA@mail.gmail.com \
--to=treapking@chromium.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=daniel@ffwll.ch \
--cc=dengshaomin@cdjrlc.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=djrscally@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hsinyi@chromium.org \
--cc=imre.deak@intel.com \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=keescook@chromium.org \
--cc=khaled.almahallawy@intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=pmalani@chromium.org \
--cc=rafael@kernel.org \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=swboyd@chromium.org \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
--cc=xji@analogixsemi.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).