linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rushikesh S Kadam <rushikesh.s.kadam@intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: srinivas.pandruvada@linux.intel.com,
	benjamin.tissoires@redhat.com, ncrews@chromium.org,
	jettrink@chromium.org, gwendal@google.com,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v5] HID: intel-ish-hid: ISH firmware loader client driver
Date: Wed, 3 Apr 2019 19:05:11 +0530	[thread overview]
Message-ID: <20190403133510.GA12574@intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1904031510430.9803@cbobk.fhfr.pm>

On Wed, Apr 03, 2019 at 03:11:02PM +0200, Jiri Kosina wrote:
> On Tue, 2 Apr 2019, Rushikesh S Kadam wrote:
> 
> > This driver adds support for loading Intel Integrated
> > Sensor Hub (ISH) firmware from host file system to ISH
> > SRAM and start execution.
> > 
> > At power-on, the ISH subsystem shall boot to an interim
> > Shim loader-firmware, which shall expose an ISHTP loader
> > device.
> > 
> > The driver implements an ISHTP client that communicates
> > with the Shim ISHTP loader device over the intel-ish-hid
> > stack, to download the main ISH firmware.
> > 
> > Signed-off-by: Rushikesh S Kadam <rushikesh.s.kadam@intel.com>
> > Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> > Acked-by: Nick Crews <ncrews@chromium.org>
> > Tested-by: Jett Rink <jettrink@chromium.org>
> 
> Now queued in for-5.2/ish. Thanks,
> 
> -- 
> Jiri Kosina
> SUSE Labs
> 

Thanks Jirk & all for help with this. 

Rushikesh

-- 

      reply	other threads:[~2019-04-03 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  5:47 [PATCH v5] HID: intel-ish-hid: ISH firmware loader client driver Rushikesh S Kadam
2019-04-03 13:11 ` Jiri Kosina
2019-04-03 13:35   ` Rushikesh S Kadam [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=20190403133510.GA12574@intel.com \
    --to=rushikesh.s.kadam@intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=gwendal@google.com \
    --cc=jettrink@chromium.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncrews@chromium.org \
    --cc=srinivas.pandruvada@linux.intel.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).