mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: John Garry <john.garry@huawei.com>, <xuwei5@huawei.com>
Cc: <arm@kernel.org>, <linuxarm@huawei.com>,
	<linux-kernel@vger.kernel.org>, <olof@lixom.net>
Subject: Re: [PATCH] HISI LPC: Don't fail probe for unrecognised child devices
Date: Fri, 8 Feb 2019 09:49:16 +0000	[thread overview]
Message-ID: <249f851b-e28c-c5df-7706-f7212162bae7@hisilicon.com> (raw)
In-Reply-To: <1546516622-46343-1-git-send-email-john.garry@huawei.com>

Hi John,

On 1/3/2019 11:57 AM, John Garry wrote:
> Currently for ACPI-based FW we fail the probe for an unrecognised child
> HID.
> 
> However, there is FW in the field with LPC child devices having fake HIDs,
> namely "IPI0002", which was an IPMI device invented to support the
> initial out-of-tree LPC host driver, different from the final mainline
> version.
> 
> To provide compatibility support for these dodgy FWs, just discard the
> unrecognised HIDs instead of failing the probe altogether.
> 
> Tested-by: Zengruan Ye <yezengruan@huawei.com>
> Signed-off-by: John Garry <john.garry@huawei.com>

Updated the subject as "bus: hisi_lpc: xxx" to follow the style and
applied to the hisilicon tree.
Thanks!

Best Regards,
Wei

> 
> diff --git a/drivers/bus/hisi_lpc.c b/drivers/bus/hisi_lpc.c
> index d5f8545..19d7b6f 100644
> --- a/drivers/bus/hisi_lpc.c
> +++ b/drivers/bus/hisi_lpc.c
> @@ -522,10 +522,9 @@ static int hisi_lpc_acpi_probe(struct device *hostdev)
>  
>  		if (!found) {
>  			dev_warn(hostdev,
> -				 "could not find cell for child device (%s)\n",
> +				 "could not find cell for child device (%s), discarding\n",
>  				 hid);
> -			ret = -ENODEV;
> -			goto fail;
> +			continue;
>  		}
>  
>  		pdev = platform_device_alloc(cell->name, PLATFORM_DEVID_AUTO);
> 


      parent reply	other threads:[~2019-02-08  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 11:57 John Garry
2019-01-04 22:25 ` Olof Johansson
2019-01-07 10:31   ` John Garry
2019-02-08  9:49 ` Wei Xu [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=249f851b-e28c-c5df-7706-f7212162bae7@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=arm@kernel.org \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=olof@lixom.net \
    --cc=xuwei5@huawei.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

all inboxes | Powered by JetHome®