From: Neil Armstrong <neil.armstrong@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Andersson <andersson@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: typec-mux: nb7vpq904m: broadcast typec state to next mux
Date: Thu, 6 Jun 2024 14:53:38 +0200 [thread overview]
Message-ID: <8568359e-840a-4fa4-bcbd-a0029e854f69@linaro.org> (raw)
In-Reply-To: <jdqnlfuqount32ralk4jr3beobdt7dgs3h4lcpxj5fbmanysl6@pgwqeozl7ow5>
On 27/05/2024 11:18, Dmitry Baryshkov wrote:
> On Mon, May 27, 2024 at 09:45:30AM +0200, Neil Armstrong wrote:
>> In the Type-C graph, the nb7vpq904m retimer is in between the USB-C
>> connector and the USB3/DP combo PHY, and this PHY also requires the
>> USB-C mode events to properly set-up the SuperSpeed Lanes functions
>> to setup USB3-only, USB3 + DP Altmode or DP Altmode only on the 4 lanes.
>>
>> Update the nb7vpq904m retimer to get an optional type-c mux on the next
>> endpoint, and broadcast the received mode to it.
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> drivers/usb/typec/mux/nb7vpq904m.c | 29 +++++++++++++++++++++++++++--
>> 1 file changed, 27 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/typec/mux/nb7vpq904m.c b/drivers/usb/typec/mux/nb7vpq904m.c
>> index b17826713753..efb10f890fed 100644
>> --- a/drivers/usb/typec/mux/nb7vpq904m.c
>> +++ b/drivers/usb/typec/mux/nb7vpq904m.c
>> @@ -69,6 +69,7 @@ struct nb7vpq904m {
>>
>> bool swap_data_lanes;
>> struct typec_switch *typec_switch;
>> + struct typec_mux *typec_mux;
>>
>> struct mutex lock; /* protect non-concurrent retimer & switch */
>>
>> @@ -275,6 +276,7 @@ static int nb7vpq904m_sw_set(struct typec_switch_dev *sw, enum typec_orientation
>> static int nb7vpq904m_retimer_set(struct typec_retimer *retimer, struct typec_retimer_state *state)
>> {
>> struct nb7vpq904m *nb7 = typec_retimer_get_drvdata(retimer);
>> + struct typec_mux_state mux_state;
>> int ret = 0;
>>
>> mutex_lock(&nb7->lock);
>> @@ -292,7 +294,14 @@ static int nb7vpq904m_retimer_set(struct typec_retimer *retimer, struct typec_re
>>
>> mutex_unlock(&nb7->lock);
>>
>> - return ret;
>> + if (ret)
>> + return ret;
>> +
>> + mux_state.alt = state->alt;
>> + mux_state.data = state->data;
>> + mux_state.mode = state->mode;
>> +
>> + return typec_mux_set(nb7->typec_mux, &mux_state);
>> }
>>
>> static const struct regmap_config nb7_regmap = {
>> @@ -411,9 +420,16 @@ static int nb7vpq904m_probe(struct i2c_client *client)
>> return dev_err_probe(dev, PTR_ERR(nb7->typec_switch),
>> "failed to acquire orientation-switch\n");
>>
>> + nb7->typec_mux = fwnode_typec_mux_get(dev->fwnode);
>> + if (IS_ERR(nb7->typec_mux)) {
>> + ret = dev_err_probe(dev, PTR_ERR(nb7->typec_mux),
>> + "Failed to acquire mode-switch\n");
>> + goto err_switch_put;
>> + }
>> +
>> ret = nb7vpq904m_parse_data_lanes_mapping(nb7);
>> if (ret)
>> - return ret;
>> + goto err_mux_put;
>>
>> ret = regulator_enable(nb7->vcc_supply);
>> if (ret)
>> @@ -456,6 +472,12 @@ static int nb7vpq904m_probe(struct i2c_client *client)
>> gpiod_set_value(nb7->enable_gpio, 0);
>> regulator_disable(nb7->vcc_supply);
>>
>> +err_mux_put:
>> + typec_mux_put(nb7->typec_mux);
>> +
>> +err_switch_put:
>> + typec_switch_put(nb7->typec_switch);
>
> Same comment, typec_switch_put should go to a separate commit. IMHO it
> almost begs us to have devm_fwnode_typec_mux_get() and
> devm_fwnode_typec_switch_get().
Yep
Thx,
Neil
>
>> +
>> return ret;
>> }
>>
>> @@ -469,6 +491,9 @@ static void nb7vpq904m_remove(struct i2c_client *client)
>> gpiod_set_value(nb7->enable_gpio, 0);
>>
>> regulator_disable(nb7->vcc_supply);
>> +
>> + typec_mux_put(nb7->typec_mux);
>> + typec_switch_put(nb7->typec_switch);
>> }
>>
>> static const struct i2c_device_id nb7vpq904m_table[] = {
>>
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2024-06-06 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:45 [PATCH 0/2] usb: typec-mux: broadcast typec state to next mux for ptn36502 & nb7vpq904m retimers Neil Armstrong
2024-05-27 7:45 ` [PATCH 1/2] usb: typec-mux: ptn36502: broadcast typec state to next mux Neil Armstrong
2024-05-27 9:16 ` Dmitry Baryshkov
2024-06-06 12:53 ` Neil Armstrong
2024-05-27 7:45 ` [PATCH 2/2] usb: typec-mux: nb7vpq904m: " Neil Armstrong
2024-05-27 9:18 ` Dmitry Baryshkov
2024-06-06 12:53 ` Neil Armstrong [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=8568359e-840a-4fa4-bcbd-a0029e854f69@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luca.weiss@fairphone.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