From: Manivannan Sadhasivam <mani@kernel.org>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: mani@kernel.org, quic_hemantk@quicinc.com,
quic_bbhatt@quicinc.com, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeffrey Hugo <jhugo@codeaurora.org>
Subject: Re: [PATCH v2] bus: mhi: host: Add soc_reset sysfs
Date: Mon, 18 Apr 2022 11:16:49 +0530 [thread overview]
Message-ID: <20220418054649.GB7431@thinkpad> (raw)
In-Reply-To: <1649883619-17609-1-git-send-email-quic_jhugo@quicinc.com>
On Wed, Apr 13, 2022 at 03:00:19PM -0600, Jeffrey Hugo wrote:
> From: Jeffrey Hugo <jhugo@codeaurora.org>
>
> The MHI bus supports a standardized hardware reset, which is known as the
> "SoC Reset". This reset is similar to the reset sysfs for PCI devices -
> a hardware mechanism to reset the state back to square one.
>
> The MHI SoC Reset is described in the spec as a reset of last resort. If
> some unrecoverable error has occurred where other resets have failed, SoC
> Reset is the "big hammer" that ungracefully resets the device. This is
> effectivly the same as yanking the power on the device, and reapplying it.
> However, depending on the nature of the particular issue, the underlying
> transport link may remain active and configured. If the link remains up,
> the device will flag a MHI system error early in the boot process after
> the reset is executed, which allows the MHI bus to process a fatal error
> event, and clean up appropiately.
>
> While the SoC Reset is generally intended as a means of recovery when all
> else has failed, it can be useful in non-error scenarios. For example,
> if the device loads firmware from the host filesystem, the device may need
> to be fully rebooted inorder to pick up the new firmware. In this
> scenario, the system administrator may use the soc_reset sysfs to cause
> the device to pick up the new firmware that the admin placed on the
> filesystem.
>
> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
Do you need double signed-off because of change in domain?
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Thanks,
Mani
> ---
>
> v2:
> Rebase
>
> Documentation/ABI/stable/sysfs-bus-mhi | 11 +++++++++++
> drivers/bus/mhi/host/init.c | 14 ++++++++++++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/Documentation/ABI/stable/sysfs-bus-mhi b/Documentation/ABI/stable/sysfs-bus-mhi
> index ecfe766..306f63e 100644
> --- a/Documentation/ABI/stable/sysfs-bus-mhi
> +++ b/Documentation/ABI/stable/sysfs-bus-mhi
> @@ -19,3 +19,14 @@ Description: The file holds the OEM PK Hash value of the endpoint device
> read without having the device power on at least once, the file
> will read all 0's.
> Users: Any userspace application or clients interested in device info.
> +
> +What: /sys/bus/mhi/devices/.../soc_reset
> +Date: April 2022
> +KernelVersion: 5.19
> +Contact: mhi@lists.linux.dev
> +Description: Initiates a SoC reset on the MHI controller. A SoC reset is
> + a reset of last resort, and will require a complete re-init.
> + This can be useful as a method of recovery if the device is
> + non-responsive, or as a means of loading new firmware as a
> + system administration task.
> +
> diff --git a/drivers/bus/mhi/host/init.c b/drivers/bus/mhi/host/init.c
> index 04c409b..e12b210 100644
> --- a/drivers/bus/mhi/host/init.c
> +++ b/drivers/bus/mhi/host/init.c
> @@ -108,9 +108,23 @@ static ssize_t oem_pk_hash_show(struct device *dev,
> }
> static DEVICE_ATTR_RO(oem_pk_hash);
>
> +static ssize_t soc_reset_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf,
> + size_t count)
> +{
> + struct mhi_device *mhi_dev = to_mhi_device(dev);
> + struct mhi_controller *mhi_cntrl = mhi_dev->mhi_cntrl;
> +
> + mhi_soc_reset(mhi_cntrl);
> + return count;
> +}
> +static DEVICE_ATTR_WO(soc_reset);
> +
> static struct attribute *mhi_dev_attrs[] = {
> &dev_attr_serial_number.attr,
> &dev_attr_oem_pk_hash.attr,
> + &dev_attr_soc_reset.attr,
> NULL,
> };
> ATTRIBUTE_GROUPS(mhi_dev);
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-04-18 5:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 21:00 [PATCH v2] bus: mhi: host: Add soc_reset sysfs Jeffrey Hugo
2022-04-13 22:54 ` Bhaumik Vasav Bhatt
2022-04-18 5:46 ` Manivannan Sadhasivam [this message]
2022-04-18 13:45 ` Jeffrey Hugo
2022-04-18 14:00 ` Manivannan Sadhasivam
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=20220418054649.GB7431@thinkpad \
--to=mani@kernel.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_bbhatt@quicinc.com \
--cc=quic_hemantk@quicinc.com \
--cc=quic_jhugo@quicinc.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