All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	dri-devel@lists.freedesktop.org, linux-input@vger.kernel.org,
	hsinyi@google.com, devicetree@vger.kernel.org,
	yangcong5@huaqin.corp-partner.google.com,
	linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
	linux-arm-msm@vger.kernel.org,
	cros-qcom-dts-watchers@chromium.org
Subject: Re: [PATCH 0/9] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together
Date: Tue, 23 May 2023 14:39:26 -0700	[thread overview]
Message-ID: <ZG0yjuNvhnircAxA@google.com> (raw)
In-Reply-To: <20230523193017.4109557-1-dianders@chromium.org>

Hi Doug,

On Tue, May 23, 2023 at 12:27:54PM -0700, Douglas Anderson wrote:
> 
> The big motivation for this patch series is mostly described in the patch
> ("drm/panel: Add a way for other devices to follow panel state"), but to
> quickly summarize here: for touchscreens that are connected to a panel we
> need the ability to power sequence the two device together. This is not a
> new need, but so far we've managed to get by through a combination of
> inefficiency, added costs, or perhaps just a little bit of brokenness.
> It's time to do better. This patch series allows us to do better.

This seems to grow a new way of building relationship between panels and
associated devices. Can we make device_link_*() work for us?

Thanks.

-- 
Dmitry

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: dri-devel@lists.freedesktop.org,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	cros-qcom-dts-watchers@chromium.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-input@vger.kernel.org, hsinyi@google.com,
	Sam Ravnborg <sam@ravnborg.org>,
	yangcong5@huaqin.corp-partner.google.com
Subject: Re: [PATCH 0/9] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together
Date: Tue, 23 May 2023 14:39:26 -0700	[thread overview]
Message-ID: <ZG0yjuNvhnircAxA@google.com> (raw)
In-Reply-To: <20230523193017.4109557-1-dianders@chromium.org>

Hi Doug,

On Tue, May 23, 2023 at 12:27:54PM -0700, Douglas Anderson wrote:
> 
> The big motivation for this patch series is mostly described in the patch
> ("drm/panel: Add a way for other devices to follow panel state"), but to
> quickly summarize here: for touchscreens that are connected to a panel we
> need the ability to power sequence the two device together. This is not a
> new need, but so far we've managed to get by through a combination of
> inefficiency, added costs, or perhaps just a little bit of brokenness.
> It's time to do better. This patch series allows us to do better.

This seems to grow a new way of building relationship between panels and
associated devices. Can we make device_link_*() work for us?

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2023-05-23 21:39 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 19:27 [PATCH 0/9] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together Douglas Anderson
2023-05-23 19:27 ` Douglas Anderson
2023-05-23 19:27 ` [PATCH 1/9] dt-bindings: HID: i2c-hid: Add "panel" property to i2c-hid backed panels Douglas Anderson
2023-05-23 19:27   ` Douglas Anderson
2023-05-30 15:34   ` Krzysztof Kozlowski
2023-05-30 15:34     ` Krzysztof Kozlowski
2023-05-30 16:52     ` Doug Anderson
2023-05-30 16:52       ` Doug Anderson
2023-05-23 19:27 ` [PATCH 2/9] drm/panel: Check for already prepared/enabled in drm_panel Douglas Anderson
2023-05-23 19:27   ` Douglas Anderson
2023-05-24  9:52   ` Neil Armstrong
2023-05-24  9:52     ` Neil Armstrong
2023-05-24 16:57     ` Doug Anderson
2023-05-24 16:57       ` Doug Anderson
2023-05-24 16:19   ` Chris Morgan
2023-05-24 16:19     ` Chris Morgan
2023-05-24 17:04     ` Doug Anderson
2023-05-24 17:04       ` Doug Anderson
2023-05-23 19:27 ` [PATCH 3/9] drm/panel: Add a way for other devices to follow panel state Douglas Anderson
2023-05-23 19:27   ` Douglas Anderson
2023-05-23 19:27 ` [PATCH 4/9] HID: i2c-hid: Switch to SYSTEM_SLEEP_PM_OPS() Douglas Anderson
2023-05-23 19:27   ` Douglas Anderson
2023-05-23 19:27 ` [PATCH 5/9] HID: i2c-hid: Rearrange probe() to power things up later Douglas Anderson
2023-05-23 19:27   ` Douglas Anderson
2023-05-23 23:27   ` kernel test robot
2023-05-23 23:27     ` kernel test robot
2023-05-24 13:01   ` kernel test robot
2023-05-24 13:01     ` kernel test robot
2023-05-23 19:28 ` [PATCH 6/9] HID: i2c-hid: Make suspend and resume into helper functions Douglas Anderson
2023-05-23 19:28   ` Douglas Anderson
2023-05-23 19:28 ` [PATCH 7/9] HID: i2c-hid: Support being a panel follower Douglas Anderson
2023-05-23 19:28   ` Douglas Anderson
2023-05-24  0:28   ` kernel test robot
2023-05-24  0:28     ` kernel test robot
2023-05-24 15:37   ` kernel test robot
2023-05-24 15:37     ` kernel test robot
2023-05-24 17:29   ` Doug Anderson
2023-05-24 17:29     ` Doug Anderson
2023-05-23 19:28 ` [PATCH 8/9] HID: i2c-hid: Do panel follower work on the system_wq Douglas Anderson
2023-05-23 19:28   ` Douglas Anderson
2023-05-24  1:36   ` kernel test robot
2023-05-24  1:36     ` kernel test robot
2023-05-24 18:56   ` kernel test robot
2023-05-24 18:56     ` kernel test robot
2023-05-23 19:28 ` [PATCH 9/9] arm64: dts: qcom: sc7180: Link trogdor touchscreens to the panels Douglas Anderson
2023-05-23 19:28   ` Douglas Anderson
2023-05-23 21:39 ` Dmitry Torokhov [this message]
2023-05-23 21:39   ` [PATCH 0/9] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together Dmitry Torokhov
2023-05-23 23:52   ` Doug Anderson
2023-05-23 23:52     ` Doug Anderson
2023-05-26 19:29 ` Konrad Dybcio
2023-05-26 19:29   ` Konrad Dybcio

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=ZG0yjuNvhnircAxA@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=andersson@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hsinyi@google.com \
    --cc=jikos@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tzimmermann@suse.de \
    --cc=yangcong5@huaqin.corp-partner.google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.