On Thu, May 4, 2023 at 12:51 AM Maxime Ripard wrote:
>
> Hi Saravana,
>
> On Wed, May 03, 2023 at 09:40:05PM -0700, Saravana Kannan wrote:
> > On Fri, Mar 17, 2023 at 3:36 PM Saravana Kannan
> > wrote:
> > >
> > > On Sun, Mar 12, 2023
On Fri, Mar 17, 2023 at 3:36 PM Saravana Kannan wrote:
>
> On Sun, Mar 12, 2023 at 7:45 AM Martin Kepplinger
> wrote:
> >
> > Am Donnerstag, dem 09.03.2023 um 22:39 -0800 schrieb Saravana Kannan:
> > > After commit 3fb16866b51d ("driver core: fw_devlink: Mak
On Sun, Mar 12, 2023 at 7:45 AM Martin Kepplinger
wrote:
>
> Am Donnerstag, dem 09.03.2023 um 22:39 -0800 schrieb Saravana Kannan:
> > After commit 3fb16866b51d ("driver core: fw_devlink: Make cycle
> > detection more robust"), fw_devlink prints an error when consumer
kernel.org/lkml/2a8e407f4f18c9350f8629a2b5fa18673355b2ae.ca...@puri.sm/
Fixes: 068a00233969 ("drm: Add MIPI DSI bus support")
Signed-off-by: Saravana Kannan
---
drivers/gpu/drm/drm_mipi_dsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drive
On Thu, Oct 7, 2021 at 1:11 PM Stephen Boyd wrote:
>
> Quoting Stephen Boyd (2021-10-07 11:40:07)
> > Quoting Saravana Kannan (2021-10-06 20:07:11)
> > > On Wed, Oct 6, 2021 at 12:38 PM Stephen Boyd wrote:
> > > > diff --git a/drivers/base/component.c b/drive
k across mipi_dsi bus devices too. This
feature avoid unnecessary probe deferrals of mipi_dsi devices, defers
consumers of
mipi_dsi devices till the mipi_dsi devices probe, and allows mipi_dsi drivers to
implement sync_state() callbacks.
Reviewed-by: Saravana Kannan
Thanks,
Saravana
>
> Sugg
On Tue, Jun 15, 2021 at 8:50 AM Sasha Levin wrote:
>
> From: Saravana Kannan
>
> [ Upstream commit 9bf3797796f570b34438235a6a537df85832bdad ]
>
> On sunxi boards that use HDMI output, HDMI device probe keeps being
> avoided indefinitely with these repeated messages in
On Mon, Jun 7, 2021 at 4:41 AM Maxime Ripard wrote:
>
> On Mon, Jun 07, 2021 at 10:58:36AM +0200, Ondrej Jirman wrote:
> > From: Saravana Kannan
> >
> > On sunxi boards that use HDMI output, HDMI device probe keeps being
> > avoided indefinitely with th
t the struct device that was being
> used is actually the parent of the aggregate device and driver.
>
> Cc: Daniel Vetter
> Cc: "Rafael J. Wysocki"
> Cc: Rob Clark
> Cc: Russell King
> Cc: Saravana Kannan
> Signed-off-by: Stephen Boyd
> ---
> drivers/base/c
On Wed, May 19, 2021 at 6:41 PM Stephen Boyd wrote:
>
> Quoting Saravana Kannan (2021-05-19 18:27:50)
> > On Wed, May 19, 2021 at 5:25 PM Stephen Boyd wrote:
> > >
> > > This series is from discussion we had on reordering the device lists for
> > > dr
describing the square wave pin
> as fixed-clock, which is registered early and basically how
> this pin is used on the i.MX6.
>
> Suggested-by: Saravana Kannan
> Signed-off-by: Sebastian Reichel
> ---
> Documentation/devicetree/bindings/rtc/rtc-m41t80.txt | 9 +
> dr
Dave Airlie wrote:
This is more about initial development stages. We maintain kernel
API/ABI for all in-tree drivers, however before we put a driver into
mainline, we usually need to redo the crazy interfaces that vendors
have come up with. Like 32/64 alignment, passing userspace addresses
into t
Dave Airlie wrote:
> This is more about initial development stages. We maintain kernel
> API/ABI for all in-tree drivers, however before we put a driver into
> mainline, we usually need to redo the crazy interfaces that vendors
> have come up with. Like 32/64 alignment, passing userspace addresses
13 matches
Mail list logo