ARM Sunxi Platform Development
 help / color / mirror / Atom feed
* [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init
@ 2026-11-17 13:00 Roadbobek via B4 Relay
  2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Roadbobek via B4 Relay @ 2026-11-17 13:00 UTC (permalink / raw)
  To: Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Philipp Zabel, Vinod Koul, Neil Armstrong,
	Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy,
	Roadbobek

When a bootloader such as U-Boot (for example with
CONFIG_USB_MUSB_HOST=y) initializes USB host mode and boots Linux
without stopping USB first, both the MUSB controller and USB0 PHY
reset lines are already deasserted when Linux probes them.

Because reset_control_deassert() alone is a no-op on an already
deasserted reset line, stale hardware register state persists across
boot. On Allwinner A33, MUSB stays wedged in a_wait_bcon with
DevCtl=0x99, Power=0xf0, and a frozen Frame counter even across
hot-unplug and replug.

This two-patch series briefly asserts reset before deasserting it in
both drivers so USB starts cleanly regardless of prior bootloader state:

- Patch 1 asserts glue->rst in sunxi_musb_init().
- Patch 2 asserts phy->reset in sun4i_usb_phy_init().

Tested on an Allwinner A33 Q8 tablet (Laser MID-786).

Signed-off-by: Roadbobek <admin@roadbobek.com>
---
Roadbobek (2):
      usb: musb: sunxi: Assert reset before deasserting on init
      phy: sun4i-usb: Assert reset before deasserting in phy init

 drivers/phy/allwinner/phy-sun4i-usb.c | 2 ++
 drivers/usb/musb/sunxi.c              | 3 +++
 2 files changed, 5 insertions(+)
---
base-commit: 666539eecdf4db623f5e3c3e55cf9f2dfad24aa4
change-id: 20261117-usb-sunxi-reset-fix-d1a0001440a9

Best regards,
--  
Roadbobek <admin@roadbobek.com>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* [PATCH 1/2] usb: musb: sunxi: Assert reset before deasserting on init
  2026-11-17 13:00 [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Roadbobek via B4 Relay
@ 2026-11-17 13:00 ` Roadbobek via B4 Relay
  2026-11-17 13:05   ` Philipp Zabel
  2026-11-17 13:09   ` sashiko-bot
  2026-11-17 13:00 ` [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init Roadbobek via B4 Relay
  2026-11-17 13:04 ` [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Philipp Zabel
  2 siblings, 2 replies; 8+ messages in thread
From: Roadbobek via B4 Relay @ 2026-11-17 13:00 UTC (permalink / raw)
  To: Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Philipp Zabel, Vinod Koul, Neil Armstrong,
	Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy,
	Roadbobek

From: Roadbobek <admin@roadbobek.com>

When a bootloader such as U-Boot (for example with
CONFIG_USB_MUSB_HOST=y) initializes MUSB and boots Linux
without stopping USB first, the controller reset line is
already deasserted at probe time.

In that case reset_control_deassert() in sunxi_musb_init()
is a no-op and stale MUSB register state persists across boot.
On Allwinner A33, MUSB stays wedged in a_wait_bcon with
DevCtl=0x99, Power=0xf0, and a frozen Frame counter even
across hot-unplug and replug.

Assert glue->rst briefly before deasserting it when
SUNXI_MUSB_FL_HAS_RESET is set so MUSB starts cleanly.
Tested on an Allwinner A33 Q8 tablet (Laser MID-786).

Signed-off-by: Roadbobek <admin@roadbobek.com>
---
 drivers/usb/musb/sunxi.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/usb/musb/sunxi.c b/drivers/usb/musb/sunxi.c
index a17b1c150626..3d16049e53b5 100644
--- a/drivers/usb/musb/sunxi.c
+++ b/drivers/usb/musb/sunxi.c
@@ -9,6 +9,7 @@
  */
 
 #include <linux/clk.h>
+#include <linux/delay.h>
 #include <linux/err.h>
 #include <linux/extcon.h>
 #include <linux/io.h>
@@ -239,6 +240,8 @@ static int sunxi_musb_init(struct musb *musb)
 		goto error_sram_release;
 
 	if (test_bit(SUNXI_MUSB_FL_HAS_RESET, &glue->flags)) {
+		reset_control_assert(glue->rst);
+		usleep_range(10, 20);
 		ret = reset_control_deassert(glue->rst);
 		if (ret)
 			goto error_clk_disable;

-- 
2.53.0



^ permalink raw reply related	[flat|nested] 8+ messages in thread

* [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init
  2026-11-17 13:00 [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Roadbobek via B4 Relay
  2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
@ 2026-11-17 13:00 ` Roadbobek via B4 Relay
  2026-11-17 13:04   ` Philipp Zabel
  2026-11-17 13:25   ` sashiko-bot
  2026-11-17 13:04 ` [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Philipp Zabel
  2 siblings, 2 replies; 8+ messages in thread
From: Roadbobek via B4 Relay @ 2026-11-17 13:00 UTC (permalink / raw)
  To: Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Philipp Zabel, Vinod Koul, Neil Armstrong,
	Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy,
	Roadbobek

From: Roadbobek <admin@roadbobek.com>

When a bootloader initializes USB before booting Linux without
first tearing down the controller, phy->reset may already be
deasserted when sun4i_usb_phy_init() runs.

Because reset_control_deassert() alone is a no-op on an
already deasserted reset line, stale USB PHY state can
persist across the bootloader-to-kernel handoff.

Assert phy->reset briefly before deasserting it in
sun4i_usb_phy_init() so the PHY starts cleanly regardless of
prior bootloader USB usage. Tested on an Allwinner A33 Q8
tablet (Laser MID-786).

Signed-off-by: Roadbobek <admin@roadbobek.com>
---
 drivers/phy/allwinner/phy-sun4i-usb.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/phy/allwinner/phy-sun4i-usb.c b/drivers/phy/allwinner/phy-sun4i-usb.c
index f26eed0db17e..05e6dcf035a1 100644
--- a/drivers/phy/allwinner/phy-sun4i-usb.c
+++ b/drivers/phy/allwinner/phy-sun4i-usb.c
@@ -270,6 +270,8 @@ static int sun4i_usb_phy_init(struct phy *_phy)
 		return ret;
 	}
 
+	reset_control_assert(phy->reset);
+	usleep_range(10, 20);
 	ret = reset_control_deassert(phy->reset);
 	if (ret) {
 		clk_disable_unprepare(phy->clk2);

-- 
2.53.0



^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init
  2026-11-17 13:00 [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Roadbobek via B4 Relay
  2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
  2026-11-17 13:00 ` [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init Roadbobek via B4 Relay
@ 2026-11-17 13:04 ` Philipp Zabel
  2 siblings, 0 replies; 8+ messages in thread
From: Philipp Zabel @ 2026-11-17 13:04 UTC (permalink / raw)
  To: admin, Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Vinod Koul, Neil Armstrong, Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy

On Di, 2026-11-17 at 13:00 +0000, Roadbobek via B4 Relay wrote:
> When a bootloader such as U-Boot (for example with
> CONFIG_USB_MUSB_HOST=y) initializes USB host mode and boots Linux
> without stopping USB first, both the MUSB controller and USB0 PHY
> reset lines are already deasserted when Linux probes them.
> 
> Because reset_control_deassert() alone is a no-op on an already
> deasserted reset line, stale hardware register state persists across
> boot. On Allwinner A33, MUSB stays wedged in a_wait_bcon with
> DevCtl=0x99, Power=0xf0, and a frozen Frame counter even across
> hot-unplug and replug.
> 
> This two-patch series briefly asserts reset before deasserting it in
> both drivers so USB starts cleanly regardless of prior bootloader state:
> 
> - Patch 1 asserts glue->rst in sunxi_musb_init().
> - Patch 2 asserts phy->reset in sun4i_usb_phy_init().

While you are at it, could you also replace the
devm_reset_control_get() calls with devm_reset_control_get_exclusive(),
to make it clear the driver requires exclusive access to assert the
resets?

regards
Philipp

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init
  2026-11-17 13:00 ` [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init Roadbobek via B4 Relay
@ 2026-11-17 13:04   ` Philipp Zabel
  2026-11-17 13:25   ` sashiko-bot
  1 sibling, 0 replies; 8+ messages in thread
From: Philipp Zabel @ 2026-11-17 13:04 UTC (permalink / raw)
  To: admin, Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Vinod Koul, Neil Armstrong, Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy

On Di, 2026-11-17 at 13:00 +0000, Roadbobek via B4 Relay wrote:
> From: Roadbobek <admin@roadbobek.com>
> 
> When a bootloader initializes USB before booting Linux without
> first tearing down the controller, phy->reset may already be
> deasserted when sun4i_usb_phy_init() runs.
> 
> Because reset_control_deassert() alone is a no-op on an
> already deasserted reset line, stale USB PHY state can
> persist across the bootloader-to-kernel handoff.
> 
> Assert phy->reset briefly before deasserting it in
> sun4i_usb_phy_init() so the PHY starts cleanly regardless of
> prior bootloader USB usage. Tested on an Allwinner A33 Q8
> tablet (Laser MID-786).
> 
> Signed-off-by: Roadbobek <admin@roadbobek.com>
> ---
>  drivers/phy/allwinner/phy-sun4i-usb.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/phy/allwinner/phy-sun4i-usb.c b/drivers/phy/allwinner/phy-sun4i-usb.c
> index f26eed0db17e..05e6dcf035a1 100644
> --- a/drivers/phy/allwinner/phy-sun4i-usb.c
> +++ b/drivers/phy/allwinner/phy-sun4i-usb.c
> @@ -270,6 +270,8 @@ static int sun4i_usb_phy_init(struct phy *_phy)
>  		return ret;
>  	}
>  
> +	reset_control_assert(phy->reset);

No error handling?

> +	usleep_range(10, 20);
>  	ret = reset_control_deassert(phy->reset);
>  	if (ret) {
>  		clk_disable_unprepare(phy->clk2);

regards
Philipp

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH 1/2] usb: musb: sunxi: Assert reset before deasserting on init
  2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
@ 2026-11-17 13:05   ` Philipp Zabel
  2026-11-17 13:09   ` sashiko-bot
  1 sibling, 0 replies; 8+ messages in thread
From: Philipp Zabel @ 2026-11-17 13:05 UTC (permalink / raw)
  To: admin, Bin Liu, Greg Kroah-Hartman, Chen-Yu Tsai, Jernej Skrabec,
	Samuel Holland, Vinod Koul, Neil Armstrong, Manivannan Sadhasivam
  Cc: linux-usb, linux-arm-kernel, linux-sunxi, linux-kernel, linux-phy

On Di, 2026-11-17 at 13:00 +0000, Roadbobek via B4 Relay wrote:
> From: Roadbobek <admin@roadbobek.com>
> 
> When a bootloader such as U-Boot (for example with
> CONFIG_USB_MUSB_HOST=y) initializes MUSB and boots Linux
> without stopping USB first, the controller reset line is
> already deasserted at probe time.
> 
> In that case reset_control_deassert() in sunxi_musb_init()
> is a no-op and stale MUSB register state persists across boot.
> On Allwinner A33, MUSB stays wedged in a_wait_bcon with
> DevCtl=0x99, Power=0xf0, and a frozen Frame counter even
> across hot-unplug and replug.
> 
> Assert glue->rst briefly before deasserting it when
> SUNXI_MUSB_FL_HAS_RESET is set so MUSB starts cleanly.
> Tested on an Allwinner A33 Q8 tablet (Laser MID-786).
> 
> Signed-off-by: Roadbobek <admin@roadbobek.com>
> ---
>  drivers/usb/musb/sunxi.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/usb/musb/sunxi.c b/drivers/usb/musb/sunxi.c
> index a17b1c150626..3d16049e53b5 100644
> --- a/drivers/usb/musb/sunxi.c
> +++ b/drivers/usb/musb/sunxi.c
> @@ -9,6 +9,7 @@
>   */
>  
>  #include <linux/clk.h>
> +#include <linux/delay.h>
>  #include <linux/err.h>
>  #include <linux/extcon.h>
>  #include <linux/io.h>
> @@ -239,6 +240,8 @@ static int sunxi_musb_init(struct musb *musb)
>  		goto error_sram_release;
>  
>  	if (test_bit(SUNXI_MUSB_FL_HAS_RESET, &glue->flags)) {
> +		reset_control_assert(glue->rst);

No error handling?

> +		usleep_range(10, 20);
>  		ret = reset_control_deassert(glue->rst);
>  		if (ret)
>  			goto error_clk_disable;

regards
Philipp

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH 1/2] usb: musb: sunxi: Assert reset before deasserting on init
  2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
  2026-11-17 13:05   ` Philipp Zabel
@ 2026-11-17 13:09   ` sashiko-bot
  1 sibling, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-17 13:09 UTC (permalink / raw)
  To: Roadbobek
  Cc: linux-usb, linux-sunxi, linux-phy, vkoul, neil.armstrong, olteanv

Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [High] usb: musb: sunxi: Signed-off-by trailer uses single-word handle
  Roadbobek
- [Low] usb: musb: sunxi: missing Fixes trailer for sunxi_musb_init()
  reset fix
--

commit 6fb0d83bc22980ce7dcaa8d7c886a7bcf57b0905
Author: Roadbobek <admin@roadbobek.com>

> usb: musb: sunxi: Assert reset before deasserting on init
>
> When a bootloader such as U-Boot (for example with
> CONFIG_USB_MUSB_HOST=y) initializes MUSB and boots Linux
> without stopping USB first, the controller reset line is
> already deasserted at probe time.
>
> In that case reset_control_deassert() in sunxi_musb_init()
> is a no-op and stale MUSB register state persists across boot.
> On Allwinner A33, MUSB stays wedged in a_wait_bcon with
> DevCtl=0x99, Power=0xf0, and a frozen Frame counter even
> across hot-unplug and replug.
>
> Assert glue->rst briefly before deasserting it when
> SUNXI_MUSB_FL_HAS_RESET is set so MUSB starts cleanly.
> Tested on an Allwinner A33 Q8 tablet (Laser MID-786).
>
> Signed-off-by: Roadbobek <admin@roadbobek.com>

[Severity: High]
Per Documentation/process/submitting-patches.rst, the Author header and
Signed-off-by trailer must use a real full name rather than a single-word
handle or nickname.

[Severity: Low]
Since this fixes the reset initialization in sunxi_musb_init(), should it
include:

  Fixes: 132e23775779 ("usb: musb: sunxi: Add support for musb controller in A31 SoC")

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261117-usb-sunxi-reset-fix-v1-0-c2b76e0e84e1@roadbobek.com?part=1

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init
  2026-11-17 13:00 ` [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init Roadbobek via B4 Relay
  2026-11-17 13:04   ` Philipp Zabel
@ 2026-11-17 13:25   ` sashiko-bot
  1 sibling, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-17 13:25 UTC (permalink / raw)
  To: Roadbobek
  Cc: linux-usb, linux-sunxi, linux-phy, vkoul, neil.armstrong, olteanv

Thank you for your contribution! Sashiko AI review found 3 potential
issues to consider:
- [High] phy: sun4i-usb: single-word handle in Signed-off-by trailer
- [Medium] phy: sun4i-usb: sun4i_usb_phy_init() asserts shared PHY2
  reset
- [Low] phy: sun4i-usb: missing Fixes trailer for sun4i_usb_phy_init()
  reset fix
It also noticed 1 related pre-existing issue this patch does not
introduce:
- [Medium] phy: sun4i-usb: clock reference imbalance in
  sun4i_usb_phy_init() [1]
--

commit 12bd7c6ca5df3e2bb05ffe3f4ddfe21723f76996
Author: Roadbobek <admin@roadbobek.com>

> phy: sun4i-usb: Assert reset before deasserting in phy init
>
> When a bootloader initializes USB before booting Linux without
> first tearing down the controller, phy->reset may already be
> deasserted when sun4i_usb_phy_init() runs.
>
> Because reset_control_deassert() alone is a no-op on an
> already deasserted reset line, stale USB PHY state can
> persist across the bootloader-to-kernel handoff.
>
> Assert phy->reset briefly before deasserting it in
> sun4i_usb_phy_init() so the PHY starts cleanly regardless of
> prior bootloader USB usage. Tested on an Allwinner A33 Q8
> tablet (Laser MID-786).
>
> Signed-off-by: Roadbobek <admin@roadbobek.com>

[Severity: High]
The Author header and Signed-off-by trailer use a single-word handle
(Roadbobek).  Documentation/process/submitting-patches.rst requires a
known real identity (full human name) for the Developer's Certificate of
Origin and does not allow pseudonyms or handles.

[Severity: Low]
Should this bug fix include a Fixes trailer?

  Fixes: ba4bdc9e1dc0 ("PHY: sunxi: Add driver for sunxi usb phy")

> diff --git a/drivers/phy/allwinner/phy-sun4i-usb.c b/drivers/phy/allwinner/phy-sun4i-usb.c
> index f26eed0db17ef..05e6dcf035a1a 100644
> --- a/drivers/phy/allwinner/phy-sun4i-usb.c
> +++ b/drivers/phy/allwinner/phy-sun4i-usb.c
> @@ -270,6 +270,8 @@ static int sun4i_usb_phy_init(struct phy *_phy)
>  		return ret;
>  	}
>  
> +	reset_control_assert(phy->reset);
> +	usleep_range(10, 20);
>  	ret = reset_control_deassert(phy->reset);
>  	if (ret) {
>  		clk_disable_unprepare(phy->clk2);

[Severity: Medium]
Can asserting phy->reset here disrupt other active USB PHYs when PHY2 is
initialized on SoCs with needs_phy2_siddq set (such as the Allwinner
H616)?

When sun4i_usb_phy_init() runs for PHY0, PHY1 or PHY3 on those SoCs, it
directly deasserts data->phys[2].reset and clears hci_phy_ctl_clear in
PHY2's PMU without going through phy_init(phy2->phy):

drivers/phy/allwinner/phy-sun4i-usb.c:sun4i_usb_phy_init() {
	/* Some PHYs on some SoCs need the help of PHY2 to work. */
	if (data->cfg->needs_phy2_siddq && phy->index != 2) {
		struct sun4i_usb_phy *phy2 = &data->phys[2];
...
		ret = reset_control_deassert(phy2->reset);
}

Because sun4i_usb_phy_probe() acquires each reset via
devm_reset_control_get() (exclusive, non-refcounted), later initializing
PHY2 for ehci2/ohci2 will now pulse data->phys[2].reset low for 10-20 us
(or leave it asserted if reset_control_deassert() fails) while PHY0, PHY1
or PHY3 are already active and relying on PHY2 remaining out of reset
with SIDDQ cleared.

[Severity: Medium]
This problem wasn't introduced by this patch, but in the needs_phy2_siddq
block right below in sun4i_usb_phy_init(), does [1]
clk_disable_unprepare(phy->clk2) disable the wrong clock after enabling
phy2->clk2?

drivers/phy/allwinner/phy-sun4i-usb.c:sun4i_usb_phy_init() {
		ret = clk_prepare_enable(phy2->clk2);
		if (ret) {
...
		}

		if (phy2->pmu && data->cfg->hci_phy_ctl_clear) {
			val = readl(phy2->pmu + REG_HCI_PHY_CTL);
			val &= ~data->cfg->hci_phy_ctl_clear;
			writel(val, phy2->pmu + REG_HCI_PHY_CTL);
		}

		clk_disable_unprepare(phy->clk2);
}

Initializing PHY0, PHY1 or PHY3 leaks a prepare/enable reference on
phy2->clk2, while prematurely disabling phy->clk2 and causing an
underflow in sun4i_usb_phy_exit().

[1] https://sashiko.dev/#/bug/linux-16c490f9-c5d0-4103-a9d3-3f6814c64cb4

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261117-usb-sunxi-reset-fix-v1-0-c2b76e0e84e1@roadbobek.com?part=2

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2026-11-17 13:26 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-17 13:00 [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Roadbobek via B4 Relay
2026-11-17 13:00 ` [PATCH 1/2] usb: musb: " Roadbobek via B4 Relay
2026-11-17 13:05   ` Philipp Zabel
2026-11-17 13:09   ` sashiko-bot
2026-11-17 13:00 ` [PATCH 2/2] phy: sun4i-usb: Assert reset before deasserting in phy init Roadbobek via B4 Relay
2026-11-17 13:04   ` Philipp Zabel
2026-11-17 13:25   ` sashiko-bot
2026-11-17 13:04 ` [PATCH 0/2] usb/phy: sunxi: Assert reset before deasserting on init Philipp Zabel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox