All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Janusz Krzysztofik <jmkrzyszt@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Date: Thu, 12 Jan 2023 11:53:12 +0200	[thread overview]
Message-ID: <Y7/YiMPIDN0Cf5Ky@atomide.com> (raw)
In-Reply-To: <3f2663ff-ff3f-4632-853a-ba4d38df9701@app.fastmail.com>

* Arnd Bergmann <arnd@arndb.de> [230112 09:03]:
> On Thu, Jan 12, 2023, at 09:37, Lukas Bulwahn wrote:
> > Commit 0fee2eac5c2b ("usb: phy: remove phy-isp1301-omap driver") removes
> > the Philips ISP1301 with OMAP OTG driver and its corresponding config
> > ISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for
> > OMAP1/2 chips, with corresponding configs, USB_OMAP and USB_OHCI_HCD_OMAP1,
> > need this removed driver (see "depends on ISP1301_OMAP") to build.
> >
> > Remove those two drivers.
> >
> > With the config USB_OMAP removed in this commit, remove some further code
> > in the omap-dma header and mach-omap1 architecture code.
> >
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> 
> This would be a great cleanup because of the simplications of the
> omap-dma code. I had previously looked at it and concluded that
> the driver is still in use though, and I think my mistake was
> just in the Kconfig part of this patch:

It sure would be nice to drop the old custom dma api in omap-dma.c
while keeping the dma.c in arch/arm/mach-omap1.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Janusz Krzysztofik <jmkrzyszt@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips
Date: Thu, 12 Jan 2023 11:53:12 +0200	[thread overview]
Message-ID: <Y7/YiMPIDN0Cf5Ky@atomide.com> (raw)
In-Reply-To: <3f2663ff-ff3f-4632-853a-ba4d38df9701@app.fastmail.com>

* Arnd Bergmann <arnd@arndb.de> [230112 09:03]:
> On Thu, Jan 12, 2023, at 09:37, Lukas Bulwahn wrote:
> > Commit 0fee2eac5c2b ("usb: phy: remove phy-isp1301-omap driver") removes
> > the Philips ISP1301 with OMAP OTG driver and its corresponding config
> > ISP1301_OMAP. The drivers, OMAP USB Device Controller and OHCI support for
> > OMAP1/2 chips, with corresponding configs, USB_OMAP and USB_OHCI_HCD_OMAP1,
> > need this removed driver (see "depends on ISP1301_OMAP") to build.
> >
> > Remove those two drivers.
> >
> > With the config USB_OMAP removed in this commit, remove some further code
> > in the omap-dma header and mach-omap1 architecture code.
> >
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> 
> This would be a great cleanup because of the simplications of the
> omap-dma code. I had previously looked at it and concluded that
> the driver is still in use though, and I think my mistake was
> just in the Kconfig part of this patch:

It sure would be nice to drop the old custom dma api in omap-dma.c
while keeping the dma.c in arch/arm/mach-omap1.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-01-12  9:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  8:37 [PATCH 0/4] Further code removal after Arnd's latest cleanup Lukas Bulwahn
2023-01-12  8:37 ` Lukas Bulwahn
2023-01-12  8:37 ` [PATCH 1/4] ARM: s3c: remove obsolete s3c-cpu-freq header Lukas Bulwahn
2023-01-12  8:37   ` Lukas Bulwahn
2023-01-12  8:57   ` Krzysztof Kozlowski
2023-01-12  8:57     ` Krzysztof Kozlowski
2023-01-12  8:37 ` [PATCH 2/4] ARM: pxa: remove further dead code after pxa93 support removal Lukas Bulwahn
2023-01-12  8:37   ` Lukas Bulwahn
2023-01-12  9:05   ` Arnd Bergmann
2023-01-12  9:05     ` Arnd Bergmann
2023-01-12  9:26     ` Lukas Bulwahn
2023-01-12  9:26       ` Lukas Bulwahn
2023-01-12 10:30       ` Arnd Bergmann
2023-01-12 10:30         ` Arnd Bergmann
2023-01-12  8:37 ` [PATCH 3/4] usb: remove OMAP USB Device Controller and OHCI support for OMAP1/2 chips Lukas Bulwahn
2023-01-12  9:02   ` Arnd Bergmann
2023-01-12  9:02     ` Arnd Bergmann
2023-01-12  9:19     ` Lukas Bulwahn
2023-01-12  9:19       ` Lukas Bulwahn
2023-01-12  9:53       ` Arnd Bergmann
2023-01-12  9:53         ` Arnd Bergmann
2023-01-12  9:53     ` Tony Lindgren [this message]
2023-01-12  9:53       ` Tony Lindgren
2023-01-12 10:19       ` Arnd Bergmann
2023-01-12 10:19         ` Arnd Bergmann
2023-01-12 14:05         ` Aaro Koskinen
2023-01-12 14:05           ` Aaro Koskinen
2023-01-12 14:31           ` Arnd Bergmann
2023-01-12 14:31             ` Arnd Bergmann
2023-01-13  7:14             ` Tony Lindgren
2023-01-13  7:14               ` Tony Lindgren
2023-01-12  8:37 ` [PATCH 4/4] ARM: debug: remove references in DEBUG_UART_8250_SHIFT to removed configs Lukas Bulwahn
2023-01-12  8:37   ` Lukas Bulwahn

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=Y7/YiMPIDN0Cf5Ky@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=arnd@arndb.de \
    --cc=jmkrzyszt@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.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.