public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] leds: simatic-ipc-leds-gpio: make sure we have the GPIO providing driver
Date: Thu, 5 Jan 2023 11:35:48 +0200	[thread overview]
Message-ID: <Y7aZ9Mmm16HVUnnu@smile.fi.intel.com> (raw)
In-Reply-To: <20230104203005.5654f3bc@md1za8fc.ad001.siemens.net>

On Wed, Jan 04, 2023 at 08:30:05PM +0100, Henning Schild wrote:
> Am Wed, 4 Jan 2023 17:51:33 +0200
> schrieb Andy Shevchenko <andriy.shevchenko@linux.intel.com>:
> > On Wed, Jan 04, 2023 at 03:39:24PM +0100, Henning Schild wrote:
> > > Am Wed, 4 Jan 2023 14:24:30 +0000
> > > schrieb Lee Jones <lee@kernel.org>:  

...

> > > As we speak i already have the third box to eventually support,
> > > which will likely be similar but this time around with
> > > PINCTRL_ELKHARTLAKE  
> > 
> > A bit of offtopic here.
> > 
> > Are you able to get / fix / ... the firmware to work with the
> > upstreamed version of pin control driver for Intel Elkhart Lake?
> > 
> > (I'm asking this in terms of the
> > https://bugzilla.kernel.org/show_bug.cgi?id=213365)
> > 
> 
> I can not tell. At the moment i am in a Siemens internal review where i
> see code that is not even close to being ready for upstream. Somewhat
> open-coded again from what it looks like.
> 
> And i do not have the machine the code is for.
> 
> Let me say "it is complicated" but some point in time a device with
> LEDs attached to PINCTRL_ELKHARTLAKE will be proposed. Likely by me,
> when i hopefully have such a device on my desk.

Thanks for the information.

Consider above just as a point to be aware of when you come to
the productization, so we won't need another pin control driver for
the same chip.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-01-05  9:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:33 [PATCH v4] leds: simatic-ipc-leds-gpio: make sure we have the GPIO providing driver Henning Schild
2022-12-22 10:19 ` Henning Schild
2022-12-23 11:58 ` Lee Jones
2023-01-02 15:22   ` Henning Schild
2023-01-03 20:20     ` Henning Schild
2023-01-04 14:24       ` Lee Jones
2023-01-04 14:39         ` Henning Schild
2023-01-04 15:51           ` Andy Shevchenko
2023-01-04 19:30             ` Henning Schild
2023-01-05  9:35               ` Andy Shevchenko [this message]
2023-01-05 11:23                 ` Henning Schild
2023-01-19 21:02 ` Lee Jones
2023-01-23 20:48   ` Henning Schild
2023-01-24  9:46     ` Andy Shevchenko
2023-01-24 10:29       ` Lee Jones
2023-01-24 13:52         ` Henning Schild
2023-01-24 14:50           ` Henning Schild
2023-01-24 13:35       ` Henning Schild
2023-01-24 13:46         ` Andy Shevchenko
2023-01-25 17:36           ` Henning Schild
2023-01-25 17:47             ` Andy Shevchenko
2023-02-02 19:57   ` Henning Schild
2023-02-03  7:59     ` Lee Jones
2023-02-03 16:58       ` Henning Schild

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=Y7aZ9Mmm16HVUnnu@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=henning.schild@siemens.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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