From: Noam Camus <noamca@mellanox.com> To: Vineet Gupta <Vineet.Gupta1@synopsys.com>, Lada Trimasova <Lada.Trimasova@synopsys.com> Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>, "linux-snps-arc@lists.infradead.org" <linux-snps-arc@lists.infradead.org>, Alexey Brodkin <Alexey.Brodkin@synopsys.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] arc: use little endian accesses Date: Fri, 11 Mar 2016 05:07:09 +0000 [thread overview] Message-ID: <HE1PR05MB1625869B55C8FB5657477812AAB50@HE1PR05MB1625.eurprd05.prod.outlook.com> (raw) In-Reply-To: <1457636268.457.34.camel@synopsys.com> > From: Lada Trimasova <Lada.Trimasova@synopsys.com> > Sent: Thursday, March 10, 2016 8:57 PM > And for example, let's see what happens when we use "readl" in function "serial8250_early_in" in driver/tty/serial/8250. Is your DTS entry includes for serial node following entries: reg-io-width = <4> native-endian; if answer is yes you should expect (in case of big endian compilation) that: port->iotype would be equal to UPIO_MEM32BE, hence no readl() use for this case. This is how it works for me here, it sounds like your case is similar. Regards, Noam
WARNING: multiple messages have this Message-ID (diff)
From: Noam Camus <noamca@mellanox.com> To: Vineet Gupta <Vineet.Gupta1@synopsys.com>, Lada Trimasova <Lada.Trimasova@synopsys.com> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>, Alexey Brodkin <Alexey.Brodkin@synopsys.com>, "linux-snps-arc@lists.infradead.org" <linux-snps-arc@lists.infradead.org> Subject: Re: [PATCH] arc: use little endian accesses Date: Fri, 11 Mar 2016 05:07:09 +0000 [thread overview] Message-ID: <HE1PR05MB1625869B55C8FB5657477812AAB50@HE1PR05MB1625.eurprd05.prod.outlook.com> (raw) Message-ID: <20160311050709.Lq0mAOAVoV015SlXV-Wc5ZkGcz5AUSdDpuvtyWJCLXc@z> (raw) In-Reply-To: <1457636268.457.34.camel@synopsys.com> > From: Lada Trimasova <Lada.Trimasova@synopsys.com> > Sent: Thursday, March 10, 2016 8:57 PM > And for example, let's see what happens when we use "readl" in function "serial8250_early_in" in driver/tty/serial/8250. Is your DTS entry includes for serial node following entries: reg-io-width = <4> native-endian; if answer is yes you should expect (in case of big endian compilation) that: port->iotype would be equal to UPIO_MEM32BE, hence no readl() use for this case. This is how it works for me here, it sounds like your case is similar. Regards, Noam
next prev parent reply other threads:[~2016-03-11 5:07 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-09 17:21 [PATCH] arc: use little endian accesses Lada Trimasova 2016-03-10 5:05 ` Vineet Gupta 2016-03-10 5:19 ` Vineet Gupta 2016-03-10 5:19 ` Vineet Gupta 2016-03-10 7:44 ` Alexey Brodkin 2016-03-10 9:55 ` Vineet Gupta 2016-03-10 18:57 ` Lada Trimasova 2016-03-10 18:57 ` Lada Trimasova 2016-03-10 19:23 ` Arnd Bergmann 2016-03-11 12:44 ` Vineet Gupta 2016-03-12 4:20 ` Vineet Gupta 2016-03-12 4:20 ` Vineet Gupta 2016-03-11 5:07 ` Noam Camus [this message] 2016-03-11 5:07 ` Noam Camus 2016-03-10 7:45 ` Arnd Bergmann 2016-03-10 7:45 ` Arnd Bergmann 2016-03-11 5:18 ` Vineet Gupta
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=HE1PR05MB1625869B55C8FB5657477812AAB50@HE1PR05MB1625.eurprd05.prod.outlook.com \ --to=noamca@mellanox.com \ --cc=Alexey.Brodkin@synopsys.com \ --cc=Lada.Trimasova@synopsys.com \ --cc=Vineet.Gupta1@synopsys.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-snps-arc@lists.infradead.org \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).